J
Jon Davis
I fired up some .NET v2.0 code in Visual Studio 2005 and ran into
compilation errors, where the codebase I had open was referencing its own
"SortOrder" enum, and that was colliding with
System.Data.SqlClient.SortOrder. The latter entry does NOT exist in .NET
Framework v2.0, yet there it was, in my v2.0.50727 folder.
As it turned out, Orcas Beta 2, which I also installed, does NOT leave .NET
Framework v2 untouched when it installs. It replaces it with .NET 2.0
Service Pack 1 (which has not yet been released, but then, neither has
Orcas).
So much for the belief that installing Orcas side-by-side with Visual Studio
2005 in a production dev environment was safe. (I'm not sure how I convinced
myself that it was; Microsoft never recommended it. *blush*)
I am, however, really irked and annoyed that Microsoft does not versionize
their own assemblies for the GAC. System.Data.dll shows up in the GAC as
2.0.0.0, and that is just sloppy, considering that they're overriding their
assemblies with new versions.
Back to DLL hell.
Jon
compilation errors, where the codebase I had open was referencing its own
"SortOrder" enum, and that was colliding with
System.Data.SqlClient.SortOrder. The latter entry does NOT exist in .NET
Framework v2.0, yet there it was, in my v2.0.50727 folder.
As it turned out, Orcas Beta 2, which I also installed, does NOT leave .NET
Framework v2 untouched when it installs. It replaces it with .NET 2.0
Service Pack 1 (which has not yet been released, but then, neither has
Orcas).
So much for the belief that installing Orcas side-by-side with Visual Studio
2005 in a production dev environment was safe. (I'm not sure how I convinced
myself that it was; Microsoft never recommended it. *blush*)
I am, however, really irked and annoyed that Microsoft does not versionize
their own assemblies for the GAC. System.Data.dll shows up in the GAC as
2.0.0.0, and that is just sloppy, considering that they're overriding their
assemblies with new versions.
Back to DLL hell.
Jon