Working folder bug

[ajj3085]

I think I found a minor bug.

I have a folder which has a working folder inherited from it's parent. In testing my CI build script locally, I need to set the working folder via one of the build tasks (more on this in a separate post). The folder is the exact same folder it was before, but the Inherited part is gone (it's now explicitly set).

I've found that if I open the solution in VS again after the working folder, I'm told I need to rebind, work offline, or remove the bindings permanately. None of these options make sense to me; the working folder in fact has not changed (it was c:\path\solutiondir when it was inheriting, and it's still c:\path\solutiondir after being set explictely). I think Vault should be smart enough to know the path didn't change.

Thanks
Andy

[Beth]

To view your bindings in Visual Studio, go to File - Source Control - Change Source Control or File - Vault Source Control - Change Bindings. It's possible that the bindings point to a different path and inherit from there.

The bindings are hard coded to the project and the Vault GUI client is not able to make changes to that. Only VS has that capability.

I can put in a feature request. In the meantime, the work-around would be to rebind your project in VS.

Can you tell me which client you are using inside of VS? That is found under Tools - Options - Source Control - Plug-in. Is it the Vault Enhanced Client or Vault Classic Client?

[ajj3085]

Hi Beth,

Rebinding isn't really an option; the change is temporary just because I happen to be testing my build script locally. But normally I'd want to keep the inherited working folder.

I'm using the Enhanced client with VS2010. It's the client I would should be smart enough to notice the path hasn't changed. I opened the binding as you suggest, and it looks as I expect.

Andy

[Beth]

I've logged a feature request on this.

F: 15811

[ajj3085]

Great, thanks!

[Beth]

You're welcome.