VS2005 Integration Issues

DBLogic · Post by **DBLogic** » Mon Jun 11, 2007 10:27 am

Hi,

We are currently evaluating version 4 for our company with a view to using it throughout as our major source control mechanism.

We've created a test project using visual studio 2005 and the 2005 plug in. All appeared to be okay, we created a couple of branches, made different changes to each branch and merged them back to the master project. However, when we now launch the master project in VS2005 it does not appear to be under source control, and the option to add to vault is greyed out.

Also, attempting to open the project from File > Open from Vault does not work and gives no error message, i.e. the project does not load.

It is no longer prompting us for a login when opening Visual Studio as it previously did, although entering the correct credentials always resulted in an error.

Can anyone assist?

Regards,
DBLogic.

Post by **jeremy_sg** » Mon Jun 11, 2007 10:55 am

The solution might have been marked as Offline (which happens when the Login dialog is canceled). Right-click the solution and choose Online from the context menu.

DBLogic · Post by **DBLogic** » Tue Jun 12, 2007 2:08 am

Hi,

Thanks for the swift response. Unfortunately, both 'Online' and 'Offline' are greyed out on the context menu. The only source-control-related option that seems to be available is 'Unbind' (see attached screenshot).

DBLogic · Post by **DBLogic** » Tue Jun 12, 2007 3:03 am

Update: Managed to 'resolve' the issue by removing the whole solution folder structure from my local disk and re-opening from Vault, though we're a little puzzled as to what happened to cause the issue in the first place!

We checked the server log and could see nothing untowards in them. Could it have been something held in my local 'repository cache', or does this hold different information? We did try resetting the cache, but this didn't seem to make a difference.

ian_sg · Post by **ian_sg** » Tue Jun 12, 2007 10:30 am

Does %temp%\VaultVsipClient.txt exist and have contents? If so, would you be willing to send it to me?

If not, if you turn on logging for Visual Studio 2005 and reproduce the issue, a peek at that log would help us figure out what happened here.