After only 8 hours or so, I managed to get some sort of grip on this XML stuff. Then I went to the pub and fortunately the Fat Bloke wasn't there.
There appear to be the usual caveats with Microsofts cunning plan for world domination which invovle making any sane person loose the will to live after trying to wade through what version of what actually works with what.
The good news is that it appears to be reasonably straightforward to write a CSV file without knowing the xml element names.
The bad news is that information on this really basic requirement is quite hard to come by.
The Reluctant Developer never ceases to be amazed (depressed) that he always appears to be the first person in the world to ever want to do a particular, seemingly basic, task.
Just lucky I gueess
Friday, April 06, 2007
XMHell
There we were happily using CSV files and now the world and his brother (and apparently his sister, cousins and even the fat bloke down the pub) want to use XML.
I'm sure XML has some uses but for the traditional Import and Export of ordinary data records it's just a pain in the proverbial. To be fair writing out XML is pretty easy (after you have wasted a few days learning something else you didn't want to know) but importing is just a pointless exercise in using the latest technology just because it's fashionable.
The customers application is going to send us an xml file, which we then have to parse to get it into CSV format so we can import it. Why? It's just as easy (probably easier) for the app to write out a csv file in the first place. So we have a whole layer of unnecessary code that serves no useful purpose and in fact can be a problem with very large import files due to memory usage.
Plus we have to go through all the pain of working out which version of Microsoft XML is available on all Windows platforms otherwise we have additional aggravation in getting the necessary msi installed on our users machines. (To save you the trouble, use MSXML 3.0 - this is allegedly available on all Windows OS as standard)
The way forward appears to be to use XSL files to convert the XML to CSV. I'll report back after I've fallen down all the gotchas. Or I may just go to the pub and have a pint of bitter version 1.0. Unless that Fat Bloke's there of course.
I'm sure XML has some uses but for the traditional Import and Export of ordinary data records it's just a pain in the proverbial. To be fair writing out XML is pretty easy (after you have wasted a few days learning something else you didn't want to know) but importing is just a pointless exercise in using the latest technology just because it's fashionable.
The customers application is going to send us an xml file, which we then have to parse to get it into CSV format so we can import it. Why? It's just as easy (probably easier) for the app to write out a csv file in the first place. So we have a whole layer of unnecessary code that serves no useful purpose and in fact can be a problem with very large import files due to memory usage.
Plus we have to go through all the pain of working out which version of Microsoft XML is available on all Windows platforms otherwise we have additional aggravation in getting the necessary msi installed on our users machines. (To save you the trouble, use MSXML 3.0 - this is allegedly available on all Windows OS as standard)
The way forward appears to be to use XSL files to convert the XML to CSV. I'll report back after I've fallen down all the gotchas. Or I may just go to the pub and have a pint of bitter version 1.0. Unless that Fat Bloke's there of course.
Sunday, April 01, 2007
April Fool
Can we just get over the April Fool thing?
The news in the real world is now nearly always more bizarre than anything you could make up.
The world hss moved on, April Fool stories are tired, sad and not in the remotest funny.
The news in the real world is now nearly always more bizarre than anything you could make up.
The world hss moved on, April Fool stories are tired, sad and not in the remotest funny.
Subscribe to:
Posts (Atom)
