Win XP Virtual PC
-
I have a desktop PC with Win 7 pro. It also has installed vs 2008 (.NET Framework 3.5) and SQL Server 2008 and 2005 express edition. Now I have to bring support to a number of legacy applications coded in VB6 I have searched on Internet if vs6 can be installed in that operative system and found that it is necessary to download and install Win XP Virtual PC But another unsolved issue appeared, according to the readings if an app is installed under win XP Virtual PC, can be seen in win 7, and launched from there. In that point I realized that the core functions of legacy app mentioned are the massive use of ADO and DAO components. Another search was started again, related with this questions: * Will not be any problem with having two visual studio versions, vs 2008 and vs 6, despite been installed under different OS * In order to interact my vs 6 app with a database do I have to downlaod an sql server express edition and installed under the win xp virtual pc, despite the DB's already installed due to 2 different OS scenario I will appreciate any help
-
I have a desktop PC with Win 7 pro. It also has installed vs 2008 (.NET Framework 3.5) and SQL Server 2008 and 2005 express edition. Now I have to bring support to a number of legacy applications coded in VB6 I have searched on Internet if vs6 can be installed in that operative system and found that it is necessary to download and install Win XP Virtual PC But another unsolved issue appeared, according to the readings if an app is installed under win XP Virtual PC, can be seen in win 7, and launched from there. In that point I realized that the core functions of legacy app mentioned are the massive use of ADO and DAO components. Another search was started again, related with this questions: * Will not be any problem with having two visual studio versions, vs 2008 and vs 6, despite been installed under different OS * In order to interact my vs 6 app with a database do I have to downlaod an sql server express edition and installed under the win xp virtual pc, despite the DB's already installed due to 2 different OS scenario I will appreciate any help
SaturnPlanet wrote:
Will not be any problem with having two visual studio versions, vs 2008 and vs 6, despite been installed under different OS
VS2008 is installed on the host-machine, VS6 in a virtual-machine. Have you installed the XP VM yet? You'll see it is considered to be a different PC completely.
SaturnPlanet wrote:
In order to interact my vs 6 app with a database do I have to downlaod an sql server express edition and installed under the win xp virtual pc
The application in the VM should be able to connect (over TCP/IP) with the Sql Server on the host-machine.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]
-
I have a desktop PC with Win 7 pro. It also has installed vs 2008 (.NET Framework 3.5) and SQL Server 2008 and 2005 express edition. Now I have to bring support to a number of legacy applications coded in VB6 I have searched on Internet if vs6 can be installed in that operative system and found that it is necessary to download and install Win XP Virtual PC But another unsolved issue appeared, according to the readings if an app is installed under win XP Virtual PC, can be seen in win 7, and launched from there. In that point I realized that the core functions of legacy app mentioned are the massive use of ADO and DAO components. Another search was started again, related with this questions: * Will not be any problem with having two visual studio versions, vs 2008 and vs 6, despite been installed under different OS * In order to interact my vs 6 app with a database do I have to downlaod an sql server express edition and installed under the win xp virtual pc, despite the DB's already installed due to 2 different OS scenario I will appreciate any help
SaturnPlanet wrote:
two visual studio versions
If one of them is installed under Windows 7, and the other under Windows XP on the virtual machine, then they are totally separate so there will be no conflicts. I'm not sure about the second question, you could try connecting to an existing SQL server on the Windows 7 system, via its real IP address. If that does not work then you may need another version loaded in the XP system.