Aaaagh! Visual Studio .NET 2003 Enterprise Developer Trouble!

[I_R_Lee]

Just yesterday, I downloaded Visual Studio .NET 2003 Enterprise Developer from MSDN. I have installed it and everything works beautifully, apart from the help. I have installed the January 2003 version of the MSDN Library and it is intergrated with both VS 2002 and VS 2003, but it only works properly in VS 2002. When I go to any of the help options in VS 2003, it tells me that it is not available and that I need to install the library, but it then opens. I was just wondering how to shut that notification up, because I have installed and intergrated the help with VS 2003, 3 times actually, and it does it every time and it is getting rather annoying. Please could someone help?

Thanks in advance.

[steved]

You don't have VS.net 2002 and 2003 installed at the same time, do you? I'm pretty sure this isn't recommended. I'm stuck with VS.net 2003 Pro, though, so if this isn't the source of your trouble, I won't be much help otherwise.

 

Speaking of downloading VS.net 2003, is there any easy way for my organization to get a username/password using our MSDN account? We receive regular monthly MSDN updates, but we have no online support - pretty annoying when 2003 would really help me. :P

 

.steve

[Robby]

Steve, you may want to follow the link provided by Derek ...http://www.xtremedotnettalk.com/showthread.php?s=&threadid=71525

[steved]

hehehe... I don't have permission to view that thread for some reason. :)

[Robby]

here's a direct link ... http://www.3leaf.com/default/articles/ea/SBS.aspx

[steved]

Uh.... that's cute. But I fail to see how that has anything to do with running Visual Studio .NET 2002 and 2003 at the same time. The framework is just a framework - there isn't any reason to require removal of an old framework before adding a new one. Visual Studio .NET 2003, on the other hand, is a fairly incremental upgrade to 2002 - compared to running VS6 and VS.net at the same time, which operate entirely independant of one another.

 

That's just my guess. You may be running vs.NET 2002 and 2003 side by side in all their glory. :)

 

.steve

Edited April 17, 2003 by steved

[Derek Stone]

Visual Studio .NET and Visual Studio .NET 2003 are two different products. They can be installed at the same time. End story.

 

The reason for this is Visual Studio .NET will only compile applications to version 1.0 of the framework, while Visual Studio .NET 2003 will only compile applications to version 1.1 of the framework. There is no way of changing this (in reason). However, you can change a compiled application's configuration file to tell it to run off a different version of the framework. There is no guarantee that the application will run, however.

[steved]

Sorry - didn't mean to upset anybody.

 

As I said, I was only _guessing_. From my experience in the past, installing any 2 versions of a Microsoft development tool (with the exception of VS6 + VS.net) caused huge catastrophies - if it was even possible at all. (Try installing VS5 and 6 at the same time. They are 2 different products.) I now fully understand the differences between the 1.0 and 1.1 framework, and how they integrate with both versions of Visual Studio. Thank you for pointing me in the right direction.

 

I_R_Lee's question, however, regarded a misbehaving MSDN lib - not incompatibilities in the framework. Next time I won't be so hasty to help in an area I haven't had direct experience in. Sorry. If you can help him with his question regarding MSDN, I'm sure he would be most appreciative.

[Robby]

Steve, no one is upset, and don't worry about being corrected, I've been wrong on many occasion.

[I_R_Lee]

Thanks for all of your help. I've just found out what the problem was that the earliest supported version of the MSDN Library is April 2003, and it has just arrived along with a few other things. I've installed it and it works.