I am experiencing problems opening VB projects within a VirtualPC machine.
I am using VirtualPC 2007 to run a VM that has Visual Studio V6 installed on XP32 SP2. The source code is kept within Sourcesafe V6 (also installed on VM).
I have shared a directory on my host PC (D:\VirtualMach ine\Data) as D: on the VM. Thus, inside the VM, this drive just shows up as D:
When I try to open the VB project I get "Path not found..." errors, and the path it displays is "D:\\Data\src\. ..", which is incorrect. It should show "D:\\src\.. ."
The path is not defined in the vbp or vbw files.
I an unsure what is causing this mapping problem between the host PC and the Virtual Machine?
The only work-around I have found that works is to SUBST the D: drive to another letter, and then access the project through this newly mapped drive.
Any ideas??
I am using VirtualPC 2007 to run a VM that has Visual Studio V6 installed on XP32 SP2. The source code is kept within Sourcesafe V6 (also installed on VM).
I have shared a directory on my host PC (D:\VirtualMach ine\Data) as D: on the VM. Thus, inside the VM, this drive just shows up as D:
When I try to open the VB project I get "Path not found..." errors, and the path it displays is "D:\\Data\src\. ..", which is incorrect. It should show "D:\\src\.. ."
The path is not defined in the vbp or vbw files.
I an unsure what is causing this mapping problem between the host PC and the Virtual Machine?
The only work-around I have found that works is to SUBST the D: drive to another letter, and then access the project through this newly mapped drive.
Any ideas??