This article by Mark Fussell provides an in-depth overview through a climax-building top ten countdown of the best features of the core XML classes in System.Xml in the forthcoming .NET Frameworks Beta 1 release. These enable you to read, write, manipulate, and transform XML. With improvements in performance, usability, typing, and querying the XML support in the V2.0 release continues to lead the industry in innovation, standards support, and ease of use.
I work with System.Xml everyday. In its current form, it sucks. It has WAY too many exceptions when trying to read properly formed XML. It has to be MS XML or nothing essentially.
Number 9 says full XML 1.0 support. This is good news. I hope it really is.
The bad news? I only took a quick look, but it looks like I’ll have to recode a bunch of stuff in it because the properties and functions are different.
I appreciate the effor someone at Microsoft is obviously making (why else would they redesign all of the SOAP XML-RPC interfaces), but requiring a complete redesign of my web application is simply UNACCEPTABLE. I think Microsoft could learn a thing or two about backwards compatibility and API reuse from the open source development community.
You must be joking.
Actually one of the reasons of MS success is preserving backwards compatibility. With each release MS does a pretty good job of making sure that most old (legacy) software will work. Note that it doesn’t mean ALL software. Some software just needs a rewrite because of infrastructural changes made to the system.
I used to run RedHat Linux 7,8,9 and now I’m running Fedora Core 1 and I must say that things are much worse in the OSS world. If you ever tried to some compile open source software which isn’t up-to-date with the latest and the greatest (for example some useful project which didn’t get any maintenance for 3 years) you’ll note how difficult is to get it to compile properly.
OSS just doesn’t care about API and ABI stability yet. There are some projects which do, but you can count them on fingers of the experienced lumberjack.
the smart lumberjacks have ten.
totally agree with jk.
everythin about windows is getting better and better now and the future
Use Java and never have to worry about Microsoft making a API dispear over night. i.e. like the current remoting in .NET sucks so they instead of making it work are going to introduce a whole new API.
How .NET developers put up with this sort of nonsense I’ll never understand.
> How .NET developers put up with this sort of nonsense I’ll never understand.
And when Java’s AWT was so sluggish they deprecated it in loo of SWING you weren’t intially yelling. Come’on. Microsoft has built in the ease to allow a developer to specify where runtime to use very easily. As previously stated, Microsoft is king of backward compatiablity. Seriously, people are still able to run Win95 applications. That’s nearly 10 YEARS of backward compatiability. In OSS, if you can get 18 months of compatiability, thats amazing
> And when Java’s AWT was so sluggish they deprecated it in loo of SWING you weren’t intially yelling
They didn’t take it away from you. Your app continued to work with AWT and new apps could be built with SWING.
The original poster was complaining that the current API will be removed and replaced by a new API so his application will break.
Hi
Gnome is released every 6 months while windows has in 10 years around 4 releases. so you arent comparing the same stuff when you talk about compatibility
Windows 95, Windows 95 OSR2, Windows 98, Windows 98 SE, Windows ME, Windows XP, as well as another planned XP release before 2005, to make a seven releases per decade. And Jess, I’m glad Microsoft takes the time to finish the product before releasing, instead of just saying “here is what we have” every six months. Do they even have a usable file selector in GTK yet? How many apps use it? Is GFTP still GTK1.x based? Sad.