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
Jon Davis - 04 Aug 2007 00:44 GMT
This gets hairier. Seems that SP1 doesn't get installed in the Vista
environment. I came across the issue in Win2003R2, but I edited the same
codebase from within a Vista Ultimate x64 VM which had vs2005 and vs2008
both installed, but no issue there, and no SP1 showing up in the VS2005 help
splash screen.
So apparently Windows Server 2003 R2 w/ Orcas installed will get a
System.Data.SqlClient.SortOrder enum in .NET Framework 2.0, but Windows
Vista w/ Orcas installed will not.
Jon
>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
[quoted text clipped - 19 lines]
>
> Jon
Michael D. Ober - 05 Aug 2007 16:16 GMT
> This gets hairier. Seems that SP1 doesn't get installed in the Vista
> environment. I came across the issue in Win2003R2, but I edited the same
[quoted text clipped - 5 lines]
> System.Data.SqlClient.SortOrder enum in .NET Framework 2.0, but Windows
> Vista w/ Orcas installed will not.
Report the above observation to the VS development team. That's why Betas
exist - to find and fix small oversights like this.
Mike.
> Jon
>
[quoted text clipped - 21 lines]
>>
>> Jon
Michael D. Ober - 05 Aug 2007 16:16 GMT
.NET v2.0 SP1 was released a few months back.
Mike Ober.
>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
[quoted text clipped - 19 lines]
>
> Jon
Frans Bouma [C# MVP] - 06 Aug 2007 08:33 GMT
> .NET v2.0 SP1 was released a few months back.
you mean VS.NET 2005 Sp1 ?
Because the .NET 2.0 framework hasn't seen any servicepacks.
FB
> Mike Ober.
>
[quoted text clipped - 20 lines]
> >
> > Back to DLL hell.

Signature
------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------
Jon Davis - 08 Aug 2007 18:30 GMT
No, it wasn't. It was installed with Orcas.
Jon
> .NET v2.0 SP1 was released a few months back.
>
[quoted text clipped - 23 lines]
>>
>> Jon