>>>They will, it's just a matter of time. Effectively, they've been doing some of it in each version of .NET. They change things that break code, they go off in different directions, they put forth new data acess techniques, and eventually they will get rid of .NET completely and we'll have to rewrite everything again.
>>
>>Sigh.
>>
>>List one significant thing that they've broken. It's all still there!
>>
>>Yes, they've put forth new data access techniques. The old ones are still there! The new ones are built on the .NET Framework. Every language matures and adds new features, tools, and concepts.
>>
>>You have no clue what you're talking about.
>
>You're just a Microsoft apologist with no mind of your own. Stick it.

With all due respect to the trouble you took to offer a reasoned and technically based rebuttal :

Mike has actually been working in .NET for a number of years and is doing so very successfully. As I understand it from your contributions, your knowledge of .NET is limited to reading what other people frustrated about MS decisions have told you about it and you have never written anything with .NET which was then "broken" or for that matter have never written anything with .NET at all.

The idea that somehow this makes Mike the guy with no mind of his own and to label him as a "Microsoft apologist" doesn't give you a lot of credibility. I get that you are frustrated, feel that somehow MS betrayed you by not making corporate decisions that complement your business decisions and wish the world was not as it is, but "stick it" just doesn't add much to the dialogue.