I have Visual Studio.NET 2002 (academic) installed. In the interest of tidiness I'd prefer to drop my shiny new VC++.NET 2003 Standard on top of this. Is this a practical, sensible thing to do? Wouldn't this be similar to bumping from VS.NET 2002 to VS.NET 2003? Can VB.NET 2002 Academic / C#.NET 2002 Academic coexist with VC++.NET 2003 in a common IDE?
I haven't seen any error messages or complaints so far in the install process; on the other hand, I haven't actually copied any files to disk yet.

[quoted text, click to view]
tidiness I'd prefer to drop my shiny new VC++.NET 2003 Standard on top of
this. Is this a practical, sensible thing to do? Wouldn't this be similar to
bumping from VS.NET 2002 to VS.NET 2003? Can VB.NET 2002 Academic / C#.NET
2002 Academic coexist with VC++.NET 2003 in a common IDE?
[quoted text, click to view]

Separate products that use different versions of the .NET Framework and
different IDE's.
You can install Visual C++ 2003 Standard on your PC along side VS.NET 2002,
but you won't be able to "upgrade" your C++ in VS.NET 2002 with your 2003
Standard.
You'll notice that the default install location for Visual C++ 2003 Standard
is not the location of your VS.NET 2002. My advice: don't try to force the
2003 install into the 2002 directory. Bad results are almost inevitable.
As I and many others have no problems with both VS.NET 2002 and VS.NET 2003
installed on the same PC (as separate products). You should have no troubles
installing and using your C++ 2003 on the same PC as your VS.NET 2002.

--
Peter [MVP Visual Developer]
Jack of all trades, master of none.