|
|
|
start date: Fri, 3 Aug 2007 15:11:46 -0700,
posted on: microsoft.public.dotnet.framework
back
| Thread Index |
|
1
Jon Davis
|
|
2
Jon Davis
|
|
3
Michael D. Ober obermd.@.alum.mit.edu.nospam
|
|
4
Frans Bouma [C# MVP]
|
|
5
Jon Davis
|
|
6
Michael D. Ober obermd.@.alum.mit.edu.nospam
|
.NET v2 SP1 breaks some code
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
Date:Fri, 3 Aug 2007 15:11:46 -0700
Author:
|
Re: .NET v2 SP1 breaks some code
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
"Jon Davis" wrote in message
news:u0Ovzrh1HHA.4584@TK2MSFTNGP03.phx.gbl...
>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
>
>
Date:Fri, 3 Aug 2007 16:44:26 -0700
Author:
|
Re: .NET v2 SP1 breaks some code
..NET v2.0 SP1 was released a few months back.
Mike Ober.
"Jon Davis" wrote in message
news:u0Ovzrh1HHA.4584@TK2MSFTNGP03.phx.gbl...
>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
>
>
>
Date:Sun, 05 Aug 2007 15:16:07 GMT
Author:
|
Re: .NET v2 SP1 breaks some code
"Jon Davis" wrote in message
news:e946lfi1HHA.5796@TK2MSFTNGP05.phx.gbl...
> 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.
>
Report the above observation to the VS development team. That's why Betas
exist - to find and fix small oversights like this.
Mike.
> Jon
>
>
> "Jon Davis" wrote in message
> news:u0Ovzrh1HHA.4584@TK2MSFTNGP03.phx.gbl...
>>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
>>
>>
>
>
>
Date:Sun, 05 Aug 2007 15:16:08 GMT
Author:
|
Re: .NET v2 SP1 breaks some code
Michael D. Ober wrote:
> .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.
>
> "Jon Davis" wrote in message
> news:u0Ovzrh1HHA.4584@TK2MSFTNGP03.phx.gbl...
> > 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.
> >
--
------------------------------------------------------------------------
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#)
------------------------------------------------------------------------
Date:Mon, 06 Aug 2007 00:33:07 -0700
Author:
|
Re: .NET v2 SP1 breaks some code
No, it wasn't. It was installed with Orcas.
Jon
"Michael D. Ober" <obermd.@.alum.mit.edu.nospam> wrote in message
news:XQlti.14790$zA4.5088@newsread3.news.pas.earthlink.net...
> .NET v2.0 SP1 was released a few months back.
>
> Mike Ober.
>
> "Jon Davis" wrote in message
> news:u0Ovzrh1HHA.4584@TK2MSFTNGP03.phx.gbl...
>>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
>>
>>
>>
>
>
>
Date:Wed, 8 Aug 2007 10:30:22 -0700
Author:
|
|
|
