VS2005+vault 3.1.8

Miyo · Post by **Miyo** » Tue Jun 05, 2007 8:23 am

Hello everybody!!

I have a big problem in my machine ! I explain you :

- when I try to open sources from vault (File-> source control -> open from source control) with Visual Studio 2005 I have this message error :

I searched in the web but nothing concerning this problem.

Thank you for your help!!

TheFly52 · Post by **TheFly52** » Tue Jun 05, 2007 9:52 am

Hi,

i have exactly the same problem.

The solution open perfectly outside of source control.

But after injecting the solution to wault, and when trying to open it using "open from source control", the behavior is the same, "could not load project etc....".

The project directories are just not created.
Only solution root files are presents, not projects sub-directories.

Searching the web for this, and find nothing.

We are using VS2005 SP1 and Vault 3.1.8.3771.

Please help !

lbauer · Post by **lbauer** » Tue Jun 05, 2007 12:41 pm

When you use Visual Studio integration, the project must be added to Vault through Visual Studio, not with the Vault GUI Client. For a project to open properly from source control, it must have been first added to source control with Visual Studio.

Otherwise, proper bindings and source control files will not be created.

To add a project to source control, open it with Visual Studio and select File->Source Control->Add Solution to Source Control. Once you do this, you can open the project normally, from the solution file on your local drive. You do not need to open it from source control.

For another user to retrieve the project, they would Open from Source Control. Then, after the solution has been retrieved from source control, the solution can be opened normally.

See this KB article for details:

http://support.sourcegear.com/viewtopic.php?t=776

TheFly52 · Post by **TheFly52** » Wed Jun 06, 2007 2:50 am

Hi,
Thanks for response, but the procedure is the one we are applying, and the issue is clearly always there.

We are able to reproduce the issue, using the followin procedure:

A) PC1
- Taking a solution NOT under source control, loading and working locally without issue.
- Using visual studio : Add solution to source control : Done, no error
- Close vs, restart vs, reopen solution : Done, no error
- Under vault client, solution is totally ok

B) PC2
- Go to another pc
- No local solution installed, all vault working directories erased
- Open vs, "Open from source control", locate the solution, putting exactly the same local directory as PC1, ok
- Solution begin to load from vault
- Some files are retrieved, inside the correct directory. Files are exactly identicale to PC1 within the same directory (.sln, .vssscc, .scc)
- The error is displayed
- No other files or directories are retrieved from vault.
=> Solution cannot be opened on this PC2.

C) PC2
copy/pasting a non source controlled solution from PC1 to PC2 : PC2 open the solution without issue.

Thanks.

lbauer · Post by **lbauer** » Wed Jun 06, 2007 3:21 pm

Did these steps work before? Do they work with other projects, just not this project?

VS 2005 SP1 was released after Vault 3.1.8 so perhaps there are some incompatibilities.

TheFly52 · Post by **TheFly52** » Thu Jun 14, 2007 6:20 am

Hi,

yes, this was working before.

And yes, we have this issue with two differents solutions, having exactly the same symptoms on the two solutions.

We have vault licences for 3.1.8.

Seems that upgrade to lastest version is not free, could you confirm ?

lbauer · Post by **lbauer** » Thu Jun 14, 2007 6:25 am

If you have current Gold Support subscription, you can upgrade at no cost. Otherwise, you need to buy Gold Support for each license. The cost is $99 per client license.

TheFly52 · Post by **TheFly52** » Thu Jun 14, 2007 6:29 am

Hi,

no we dont have gold support licences.

This is a bit expensive for just an upgrade, and just to correct this bug... if it corrects it...

lbauer · Post by **lbauer** » Thu Jun 14, 2007 8:26 am

It's possible this is not related to the service pack -- I'll investigate to see if we have had other reports of this error.

Was this project ever moved in Vault, using the Move operation with the Vault GUI Client?

TheFly52 · Post by **TheFly52** » Thu Jun 14, 2007 9:56 am

No, not moved at all using vault.

As specified, we are taking a solution not under source control, add it to source control using VS, and on other pc, Open From Source control using VS.

TheFly52 · Post by **TheFly52** » Wed Jun 20, 2007 3:30 am

Hi,

do you have any news about this ?

Because, this begin to be very blocking for us. Some developpers cannot open our solution and cannot work on it.

We are thinking about reversing to VSS...

Thanks.