Visual Studio 6

[lambchops511]

I have Visual Studio 2005 installed.

I need to install Visual Studio 6 for the VB. Do I need to uninstall the 2005 first? or can I just go ahead and install the 6.

 

[KLin]

You need vb6? vb.net is a part of visual studio 2005.

 

[nova2]

you should install version 6 first, but I can't remember what kind of problems you may run into if you do not.
google may help you find out more

if you haven't tried yet, I'd really try to get the code to compile in vs8/2005 first if reasonably possible, but if you cannot then i guess you have a date with vs6

 

[Markbnj]

Will VB.Net not build VB 6.0 code? Anyway, I think you should be ok installing VS 6.0, but as nova2 said, typically you'd want to put the newer version on top of the older version. Since almost everything important is contained in the project settings I don't usually fret much over having to reinstall VS. If it screws you up you'll be able to recover in 30 mins or so.

 

[DaveSimmons]

Both coexist peacefully, but I've always installed VS6 before VS2003 or 5.

Microsoft has a long history of problems when installing newer versions of tools and applications first, since the older versions were never written to expect that. Not that they're alone in this, and not that I know of any specific issues.

Like everyone else suggests, you might see if the code works in VB.Net first.

 

[lambchops511]

yeah , i have some legacy applications that are in VB 6....and the client is using VB6

usually i install 6.0 before 2005 and it works fine.......

my problem is, Visual Studio 2005 is already installed....

i read some problems about installing 2005 before 6.0..........so wanted to ask if anyone has tried it and worked for them (installing 2005 BEFORE 6.0)

 

[QuixoticOne]

There are usually enough problems running only one version of their tools without asking for more by trying to run several different ones on the same PC.

That said, if you try to install them into different directories, and try to run them as different machine accounts with different user environment variables / batch files etc. that will usually help.

Honestly I'd be looking into just running the old / infrequently used version of the software inside a virtual machine like with the free VPC2007 software or VMWARE or something. That way you don't have to worry about conflicts in the filesystem.

I suppose I wouldn't be too inclined to do that unless I had at least a P4 1GHz and 2GB RAM though... but YMMV.

 

[Markbnj]

There are usually enough problems running only one version of their tools without asking for more by trying to run several different ones on the same PC.

Actually, all the VS versions live together just fine. I have at one point had 2003, 2005, and 2008 all on the same machine. At the moment I have 2005 and 2008, although with 2008 multi-targeting I won't need to keep 2005 around anymore.

However, the order of install is usually important, and you can't blame them for that. VS 2003 knows about VS 6.0, but you can hardly expect the converse to be true.

Furthermore, Microsoft's development tools are easily among the most stable and complete available, a fact that even my Eclipse-oriented brethren readily admit.

 

[Snapster]

Install VS 6.0 and do a repair on VS 2005 if you things are messed up. It should have been done the other way round but these things happen.

 

[hans007]

I have 03 and 05 on my machine and it seems to be ok. I think i installed 03 first though. Just give it a shot, i think it should work.

 

[programmer]

Shouldn't be a problem. I have VS6, VS2003.NET, VS2005, and VS2008 all installed and working properly. You do need to pay attention to which Platform SDK each refers to, but otherwise shouldn't be an issue.

 

[formulav8]

I currently have VB 6.0, VB.NET 2003, VB.NET 2005, and VB.NET 2008 installed on my computer and have absolutely NO problems. But that doesn't mean you won't have any.



Jason