Error accessing Source Code Control system VC6

[Beth]

Can you open open VC 6(without any projects being opened and go to the menu -> Project -> Source Control and show me a screenshot of what you see?

Also, I just want to verify that everything we're checking and doing happening on the XP VM. Is that correct? Since you mentioned your machine being WIndows 7 a few times, I want to make sure that you're only looking at the VM where VC6 is and where Vault should be, and that's where you're checking the registry settings. The host machine won't really affect this setup in the VM as far as I know.

[peterbrown05]

I wil lsend screen shot tomorrow. but yes,
PC Running WIndows 7
XP SP3 running in VM on the windows box. The VM that windows provide free of charge.
Ive installed VC6 and vault on the VM and all registry grabs were from the xp machine.

All windows updates have been applied to both Windows7 machine AND the XP VM.

cheers
pete

[peterbrown05]

The projects menu correctly shows Vault, clicking the link launched Vault OK.
BUTm, opening a workspace results in the same old error (see 2nd screen shot attached)

[Beth]

If you open a project that is not yet in Vault, does it allow you to add to Vault?

[peterbrown05]

unfortunately that doesnt work either.

When I open vc6 without opening a workspace, the Project->Source Control menu option is visuble
I created a dummy project
then went to Source Control->Add to Source Control...

then, the same old error message popped up "Error Accessing Source Control Systsem... etc"
then, the Source Control options remain greyed out forever more.
p

[Beth]

We recreated the scenario again here. Give this a try and let me know your results.

1) Verify what version of .Net framework the machine is using.
Create a MSDEV.EXE.Config file (if it is not already there) in "C:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin" and add the following code to it

Code: Select all

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <startup>
    <supportedRuntime version="v2.0.50727"/>
    <requiredRuntime version="v2.0.50727" safemode="true"/>
  </startup>
</configuration>

(Verify that %windir%\Microsoft.NET\Framework\v2.0.50727 does contain
mscorlib.dll)

2) Save the MSDEV.EXE.config file, and make sure that the file extension is MSDEV.EXE.config and not MSDEV.EXE.config.txt

3) Relaunch VC++ 6.0 , and Open WorkSpace dialog with Source Control.

[peterbrown05]

Beth...

guess what?

IT WORKED!

Thank you so much for all your help.

For reference, I didnt have the .config file so I created a new one.
I DID have the .dll file you mentioned.
So, all I had to do was create the .config file and it all worked.

Thank you!
peteB

[Beth]

Thanks for the update. I'm happy to hear you are working again.

[peterbrown05]

just for others reference, I have also just been trying Sun's Virtual Box.
This time I ensured that I installed Vault after Visual Studio.
Unfortunately I had the same problem as outlined above, but the fix Beth suggested above worked for that too.

So far, performance of Vault seems to be faster on the Sun Virtual Box rather than on the Microsoft Virtual Machine.


So its all working for me....
thanks again!

[Beth]

Thank you for the additional information. I'm sure other users will find the information useful.