Set working folder during Add Solution to Source Control

[mmelnick]

I'm trying to get a solution into our SGV 5.1.2 repository using the VS2010 integrated controls. The solution is located in D:\Projects\Dev\MyFancySolution but when I select File->Source Control->Add Solution to Source Control, the Add to Vault Folder dialog that I get has the working folder set to D:\Projects. Since the box is greyed out, I'm forced to accept that default when I click Ok.

How do I change that default? Presumably it has to be changed somewhere else before I click Add Solution to Source Control, but I have no idea where. I tried accepting the default with the intent of moving the folders using the SGV client after the check in, but the folders were all empty.

Some background: the solution was checked out from our old repository 4.0.2 using the 4.0.2 SGV client, cleaned (or so I thought by choosing "Permanently remove source control association bindings") of repository tags, and then moved from D:\Projects\Dev\MyFancySolutionOld to where it is now.

[lbauer]

When you add a solution to source control using the Vault Classic Client, the working folder is determined by where the solution already is on disk. I'm not sure why Visual Studio is picking up only this of the path: D:\Projects.

Is the Solution file in D:\Projects?

[mmelnick]

The solution file is in D:\Projects, but nested two subdirs lower. D:\Projects\Dev\MyFancySolution is where the sln file is and I loaded the solution into VS2010 by opening it from that directory.

I can load the solution in with the standalone SGV client. It sets the Working directory as D:\Projects as well, but in the client, I can Set Working Directory and force it back. Unfortunately, I can't open that directly from Visual Studio because of something about binding. Maybe there's a way to manually hook up the bindings so that it can be loaded into Visual Studio directly. That is my ultimate goal in the end

[lbauer]

I'd suggest we schedule a remote assist session where I can take a closer look. Email support at sourcegear.com, Attn: Linda and we'll set something up. Please include a link to this forum post.

[mmelnick]

Thanks for your help, Linda.

In case anyone else is having trouble adding an old VS2005-converted-to-VS2010-4.0.2 project into a 5.1.2 repository, we essentially did the following things:
1. Remove all *.vsp* files and *.scc* files to remove all bindings in the source tree
2. Open VS2010 and open the project from the file system
3. Change the Source Control to use the enhanced client
4. Now File->Source Control->Add to Vault

I've tested te result on two machines and it's working great.

[lbauer]

Glad it's working for you now.