Oh yeah "business alignment", thanks so much for that stuff. Hey I wonder if it tracks "lines of code written" or just lets me know which "feature" I'm supposed to be "coding" that day.
Visual Studio is locked so closely to Microsoft's platform that it cannot be prised apart and assessed in isolation. The forthcoming Visual Studio 2010, for better or worse, continues this tradition. While full details on Visual Studio 2010 are not yet available, we have been able to piece together a fair amount by attending …
>"Visual Studio is locked so closely to Microsoft's platform that it cannot be prized apart and assessed in isolation."
Where do you want to assess it, in a shoebox? If you're referring to the fact that it's in a Virtual PC image, that's how they usually preview Visual Studio releases before it comes out as it is still unstable and in an experimental stage. That's how software works if you need to release a pre-beta: You strictly define the environment.
I'm not sure if the first few paragraphs were meant to be 'attention grabbing' for lack of content in the article or not, it doesn't seem like you really were paying attention at the PDC.
We went from having copies of MSVCRT in every applications directory.... which caused DLL hell.
Then they tried forcing it to appear in System32 only, which caused another type of DLL hell.
Then they tried 'side by side', which caused a myriad of issues and would cause perfectly working applications to stop working just becuase you installed a service pack.
Now they're back to putting everything back in the applications directory.
In all this time MS never actually thought of using a lib directory (system32 would do even, although that's way too full already) and putting the version number of the library in the filename. Something that unix got right 40 years ago.
How about a new feature called "usability" where it can run OK on a machine with 2GB of RAM, and average hardware. I've never found a machine that can load/edit/run a large web app with decent performance. Oh yeah, and the latest SP causes it to crash *all* *the* *time*.
Fix it first, then improve it.
Putting version numbers in the filenames is the easy part. Just rebuilt the CRT from source (which is provided with VS2005 onwards) and call it whatever the hell you like (Except MSVCRT). There are even mak files provided to make the rebuild even easier.
On a side note, this allows you to turn any optimisations off that you may not want - e.g. Frame Pointer Ommission.
Biting the hand that feeds IT © 1998–2019