Problem accessing source code control

neal007 · Post by **neal007** » Thu Nov 01, 2007 9:54 am

Since switching to the Vault 2005 client 4.0.5 several of us have had this issue (see attached image). We have to close VS.NET 2005 and re-open it to hope it clears, which it usually will. Never had issues like this with MSSCCI.

ian_sg · Post by **ian_sg** » Thu Nov 01, 2007 2:25 pm

Just this week we discovered that directly opening a solution or project (e.g. by double-clicking in Windows Explorer) sometimes causes this (as opposed to opening via the File menu within Visual Studio). Is that applicable?

neal007 · Post by **neal007** » Thu Nov 01, 2007 2:33 pm

No - I open VS.NET which loads to an empty IDE, I then choose File...Recent Projects and open my solution from there.

neal007 · Post by **neal007** » Wed Nov 14, 2007 5:34 am

I had this problem again, very odd! I opened VS.NET, went to File...Recent Projects and opened my solution. Checked out the entire solution as I had to do run a project converter update for my DevExpress components. So I closed the solution while still checked out, ran the converter, opened the solution, checked everything in. No big deal. Later that day I went to open the solution and I could not get any of the dozen or so projects to load due to the error I posted in this thread. Not sure if it's related but I had Vault Client GUI open looking at another repository, so I don't know if something in the cache or session was causing this issue. Ultimately I had to reboot. Closing and re-opening VS.NET would not clear this which is usually all it takes. After rebooting I was able to open my solution.

neal007 · Post by **neal007** » Fri Nov 16, 2007 12:19 pm

And again I cannot get into my solution and will have to reboot. I was working on a VS 2005 solution that is using Vault 2003 client. Closed VS.NET, had lunch, came back and opened VS 2005 to work on a solution under Vault 2005 client and I get the error attached and the one already in this thread.

neal007 · Post by **neal007** » Fri Nov 16, 2007 2:08 pm

I think I have identified the problem in this situation as well. If you open VS.NET 2005 and set the Default Source Code Control to the 2003 client, it appears to have a problem detecting when a solution/project is using the Vault 2005 client. I switch among various solutions some use Vault 2003 some use Vault 2005 (VSIP). All projects within the solution are using the same client so that's not the issue.

I had rebooted this time, which usually cleared the issue, and could not get into my solution! I then for some reason decided to see if the default client had changed back to Vault 2003 as I had also done a reinstall of Vault 4.0.5 in troubleshooting this today, and once I set it to Vault 2005 I could open my solution.

So again, the problem appears to be in detecting what source code control version a solution is using. We do not have our "solutions" in vault, only our projects. Each developer has their own solution and adds the projects to the solutions but we do not check-in the .sln file itself, so it's not in source code control, if that is part of the issue.

I hope 4.0.6 is coming soon!!!

ian_sg · Post by **ian_sg** » Fri Nov 16, 2007 2:42 pm

Neal,

Thanks for the information. Detecting which source control tool is responsible is obviously done by Visual Studio before we're involved, but it's plausible that when you have an unbound solution and you work with both the MSSCCI and VSIP clients, the switch isn't always performed as it should be. We'll look into this and let you know what we find.

neal007 · Post by **neal007** » Fri Nov 16, 2007 3:11 pm

Ian,

I have no problems putting my .SLN file in vault if that will help the issue. However, I cannot figure out how to bind the SLN to vault as when I right-click on the solution (top) node, there is no option to add the solution to vault. All projects in the solution are already bound. How do I get the solution in there? I hate to add it from Vault Client directly as I don't know how it would know Vault 2005 or 2003 for the bindings.

ian_sg · Post by **ian_sg** » Fri Nov 16, 2007 3:13 pm

In 4.0.5 we added a dialog box to manage bindings and moved the command under the File menu: File->Change Vault Bindings.

neal007 · Post by **neal007** » Fri Nov 16, 2007 3:17 pm

I tried that, when I click Bind and specify the path it says "invalid" file not found. I assume I need to manually add it to vault and then bind it to the file once it's manually added? It's odd that it's not adding it to vault for me. Make sense?

ian_sg · Post by **ian_sg** » Fri Nov 16, 2007 3:18 pm

I had (erroneously) assumed the solution was in source control. Yes, in your state there's no way to automatically get it added. You'd have to add it to your repository manually, then bind it, then commit the change (as binding will writing info into the solution file).