What solution is the best between 1, 2 or 3 ?

[Golard]

Hello,
My project is actually in VB6 (Visual Studio 6) on XP.
This project is Vista compatible, and has to stay XP compatible.

I'm going to install VS2008 and migrate my project:
First step, I want to migrate my main exe in VBNet 2008 and keep all my DLL
in VB6,
Second step (later), I will migrate my all project in VBNet 2008 and get rid
of VB6.

MY QUESTION IS: What solution is the best between 1, 2 or 3 (see below)?
1= install VS2008 on the same XP PC than VS6
2= install VS2008 on another XP PC
3= install VS2008 on a Vista PC (and continue to compil all my DLL under VS6
XP)

Thank you (and sorry for my rusty english)

(Msg crosspossed in microsoft.public.dotnet.general,
microsoft.public.vsnet.general and microsoft.public.vstudio.setup)

 

[John Saunders]

Hello,
My project is actually in VB6 (Visual Studio 6) on XP.
This project is Vista compatible, and has to stay XP compatible.

I'm going to install VS2008 and migrate my project:
First step, I want to migrate my main exe in VBNet 2008 and keep all my
DLL
in VB6,
Second step (later), I will migrate my all project in VBNet 2008 and get
rid
of VB6.

MY QUESTION IS: What solution is the best between 1, 2 or 3 (see below)?
1= install VS2008 on the same XP PC than VS6
2= install VS2008 on another XP PC
3= install VS2008 on a Vista PC (and continue to compil all my DLL under
VS6
XP)

There is no reason not to install both on the same system.

 

[Golard]

There is no reason not to install both on the same system.

" There is no reason " ???
The reason is that librairies from VB6 and executables from VBNet2008 have
to come together to build my project...
You advise me to have 2 separate PCs, but which solution between 2 and 3 ?

 

[John Saunders]

" There is no reason " ???
The reason is that librairies from VB6 and executables from VBNet2008 have
to come together to build my project...
You advise me to have 2 separate PCs, but which solution between 2 and 3 ?

No, I mean you can install both on the same system.

 

[Cowboy \(Gregory A. Beamer\)]

Install on the same computer as Visual Studio 6. Visual Studio 2008 will not
do anything to your COM bits (VB6) and will not destroy or upgrade Visual
Studio 6. They are two methodologies, two paradigms and two separate
programs. There is absolutely NO conflict.

As far as migration, you can certainly create a UI and link back to the VB6
bits. You do it with tlbimp.exe. The explanation and instructions are here:
http://msdn.microsoft.com/en-us/library/ms973800.aspx

I would agree that it is probably easier to alter UI first, although I am
certain there is someone who would disagree.

--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA

Subscribe to my blog
http://feeds.feedburner.com/GregoryBeamer#

or just read it:
http://feeds.feedburner.com/GregoryBeamer

********************************************
| Think outside the box! |
********************************************