Root working directory hierarchy...

[bsapd]

I don’t really understand why Vault and the IDE integration cannot work with solutions that have projects/files outside of a common working directory. VSS can handle this just fine. I am still evaluating Vault and everything else besides this seems to work great. I read somewhere in this forum that SourceGear treats differences between VSS and Vault as bugs, does this mean that this issue is a bug to be fixed in the future? Anyway, this may just prove to be more of an annoyance than anything, but it just doesn’t always make logical sense to have all your projects follow a common hierarchy, especially with web projects.

[dan]

Yes, we do consider differences to be bugs, but I can't promise that this particular one can be fixed. We looked long and hard at it, but have not yet been able to figure out the magic incantation to get Visual Studio to send us the correct file paths when a file or project is outside the common root.

The problem is that we only get to see one side of the API, whereas MS gets to see both sides, so sometimes, something will work with VSS, and we won't know why.

However, web projects are indeed a special case, and one that should work with VS/Vault. Visual Studio will actually ask you for two folders when adding a project - one for the web project, and one for everything else (or actually, one for each web project you have in the solution). See http://support.sourcegear.com/viewtopic.php?t=35 for more info.

[bsapd]

Ok, well maybe I did something wrong then. I had a web project in VSS with a solution binding of let’s say “C:\MySolutions” and a web project binding of “C:\Inetpub\wwwroot\MyWebApp”. I imported the project into Vault using the import tool and then created a new solution from Vault. When I did that, Vault was complaining that the solution file was missing and that I had it checked out in another location. Then I got all kinds of strange errors after that. Are you saying that I should have been able to do this? If so, please help!!! This would make things a lot better. (In my real scenario I have 7 projects in my solution: 2 Web, 3 Class Libraries, and 1 Console. Everything except the web projects is in the default “Visual Studio Projects” folder.) [/b]

[dan]

If everything is in Vault correctly, try doing an Open From Source Control from within the IDE. It would be wise to not use the same working folders as before, since Vault needs to do the initial Get Latest to have baseline files (the files that exist there now would be Unknown to Vault, and that causes all sorts of problems). You could simply rename the existing working folders (so as to keep all of your existing files, in case something goes wrong), if you want to keep the same locations you have now.

[bsapd]

I did that, but it sounds like something else may have been wrong so I will try it again...