Linked by Thom Holwerda on Fri 18th Apr 2008 11:38 UTC
Windows When Vista was released, and the first reviews started to trickle in, it became apparent that Vista was a massive release - not only in terms of money spent on it by Microsoft and the amount of promotion, but also the operating system itself. It was huge, and it felt as such too. Despite what many have been saying the past year, Vista is, in fact, much more than just XP with a new theme. Basically every framework and feature has been rewritten, lots of new ones have been added, and, according to some, the process of modularisation has started with Vista (and Server 2008). It may come as no surprise that all these changes resulted in a whole boatload of bugs and breakage, which led many people to conclude that Vista was simply not as "done" as it should have been when released. Steve Ballmer confirmed these sentiments in a speech at Microsoft's Most Valuable Professionals conference in Seattle.
E-mail Print r 4   · Read More · 46 Comment(s)
Permalink for comment 310350
To read all comments associated with this story, please click here.
RE[2]: meh
by moronikos on Fri 18th Apr 2008 17:15 UTC in reply to "RE: meh"
Member since:

I also want to know why they (Microsoft) haven't moved all their operating system components over to the new WinFX/.NET - you would think if that were the future, all the bundled applications with Windows Vista would include all these new API's - but they don't.

Well, that is a good question. Originally, more of the apps did use.NET, but then they had to back away from them. I remember reading about writing Windows shell extensions and there were Microsoft published articles about the right way to do it in .NET. Later on, they recanted and said not to write shell extensions in .NET--because of .NET's own version of "DLL Hell" that could be called "Runtime Hell". Only one version of the .NET runtime can be loaded into a process space and if you have different requirements of what is the required runtime is--well, let's just say that bad things happen. That's why they had to back away from writing shell extensions in .NET.

Reply Parent Score: 2