[RESOLVED] VB .net and VB6 together in one Machine.

[zeezee]

Hi all,
I am hoping to use VS .Net together with VS 6 in the same machine.
My problem is can we use both development environments together in one machine (without multiple boots/OS) ?
Will there be any inconsistancies / conflicts using both in one machine?
Can we setup to open VB 6 projects with VB6 and VB.Net projects with VB .Net?
Please share your opinion.

Thanks in advance!

[TheBigB]

For as VB2005.net and VB6, it works for me.

But I had a friend who had some side-effects with VB6.
When he tried to open a project or close one, the MS Installer always seemed to appear.

I'd say you just try it.

[Paul M]

That problem is currently occurring with me on my computer. I'm probably going to just try and reinstall VB6 and see if that helps at all.

EDIT: As for the setup of opening files, the VB6 and VB.NET files have different extensions so opening the files with the correct program is no issue

[TheBigB]

I think it depends on the order of installation.
I've installed VB6 first and then VB2005.net.
Now it works fine.

[zeezee]

so there wont be any conflicts with vb6 components and b .net components? like ADO?

[mendhak]

They have similar names but that's where the similarity ends. So there won't be a conflict.

I have them together on one machine.

[RobDog888]

so there wont be any conflicts with vb6 components and b .net components? like ADO?

.NET uses a completely different technology for ADO. Its called ADO.NET. All the VS versions are actually completely different products/programs just like as if you had installed PhotoShop while having MS Paint on your system. They get along great just alike every single version of VS from VB6 to VB 2008. As long as you take the default install paths and dont install into the same folders then there is no conflicts or compatibility issues.

[zeezee]

ok guys. Now my fear is little bit over. I ll give it a try. |I guess there is a litte risk , but I ll give it a try and tell you.

Thank you all for your opinions.

[bgmacaw]

When he tried to open a project or close one, the MS Installer always seemed to appear.

I have this problem on my work system. Office Standard was installed when I got there (no Access). I installed VS 2005 my first day there. A few months later I had to work on some legacy code and installed VB6. Whenever I try to save a project in VB6 or exit VB6 after running a project, the install dialog for Access comes up. I'll probably re-install Office, with Access, if I have any more legacy work to do (hopefully that won't happen though).

Oh, I have both VB6 and VS 2005 installed on my home system with no problems. However, there VB6 and Office were installed long before VS 2005.

[RobDog888]

I have this problem on my work system. Office Standard was installed when I got there (no Access). I installed VS 2005 my first day there. A few months later I had to work on some legacy code and installed VB6. Whenever I try to save a project in VB6 or exit VB6 after running a project, the install dialog for Access comes up. I'll probably re-install Office, with Access, if I have any more legacy work to do (hopefully that won't happen though).

Oh, I have both VB6 and VS 2005 installed on my home system with no problems. However, there VB6 and Office were installed long before VS 2005.

What happened is a few possibilities. A a shared feature that is set for install on first use is now being used. Or the shared dialog dlls were overwritten or corrupted which office also uses. Usually just poping in the CD and installing what it request is alll that it takes to resolve it.

[bgmacaw]

What happened is a few possibilities. A a shared feature that is set for install on first use is now being used. Or the shared dialog dlls were overwritten or corrupted which office also uses. Usually just poping in the CD and installing what it request is alll that it takes to resolve it.

But as long as I don't have Access installed on my PC I don't have to support any of our Access apps.

I''m supposed to get Office 2007 installed soon though as part of a company wide upgrade. Maybe that will fix it. If not, I'll eventually have to find the MSDN CD's with Office 2000.