VS2005 and VS2003 coexistence

After installing VS2005 B2 from the Team System disk, I receive the following error when loading a 2003 project in my VS2003:

The following two files are marked as incompatible:
C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\vspackages\cslangsvc.dll
(Version 7.10.3077 [2])

C:\Windows\Microsoft.NET\Framework\v2.0.50215\cscomp.dll
(Version 8.0.50215.44(beta2.050215-4400)[4b000050])

Then compiler cannot be used in this configuration. This is usually caused by installing different flavors of VS and NDP, and not specifying the VS version for the /CompilerSourcePath and /NonNdpSourcePath options when running NdpSetup.

I thought VS2003 and VS2005 (Beta 2) can both exist on the same machine. What is NdpSetup? Any help would be appreciated.

[833 byte] By [bcasner] at [2007-12-16]
# 1
The framework service packs have the prefix "ndp", did you install one after VS2005?

I have VS03 and VS05B2 on the same machine, and it works flawlessly.

DanielRieck at 2007-9-9 > top of Msdn Tech,Visual Studio,Visual Studio Setup and Installation...
# 2

Is this text in blue the exact output? Where does it show up? In the Output window? You've never had any Microsoft-internal builds have you?

DanVallejo at 2007-9-9 > top of Msdn Tech,Visual Studio,Visual Studio Setup and Installation...
# 3
This message was in a pop-up dialog in VS2003 when the project was loading. I had installed the DotNet 1.1 SP1 from KB867460 a few months ago that could have had some effect on this. I was able to fix the problem this morning by rerunning the VS2003 install and selecting the repair option. Both seem to be happy now.
... no internal builds on this machine; only MSDN releases and no VS2005 prior to this beta 2.
bcasner at 2007-9-9 > top of Msdn Tech,Visual Studio,Visual Studio Setup and Installation...
# 4
I get the same thing with VS2002 after installing v1.1 framework. Where exactly are the 2 files marked as being incompatible? Is there some config file or something?
tushka at 2007-9-9 > top of Msdn Tech,Visual Studio,Visual Studio Setup and Installation...
# 5

I case it helps anyone...

I started receiving this error when attempting to load or create a C# project in MSVS 2003. The problem turned out to be a registry setting that I created, at a coworker's prompting, for reasons I don't remember and probably weren't all that clear to begin with:

HKLM \ Software \ Microsoft \ .NET Framework : OnlyUseLatestCLR (DWORD) = 1

If this setting is present, MSVS2003 will try to run on the .NET Framework 2.0, and fail with errors like the one above. MSVS2003 only runs on the .NET Framework 1.1, and this setting interferes with that.

BryanRaynor at 2007-9-9 > top of Msdn Tech,Visual Studio,Visual Studio Setup and Installation...
# 6
This registry value is recommend only for debugging purposes and should be either deleted or set to 0. As far as I know there are no tools or programs that will forcefully set this value to 1.
GabrielLozano-Morán at 2007-9-9 > top of Msdn Tech,Visual Studio,Visual Studio Setup and Installation...

Visual Studio

Site Classified