ASP.NET 2.0 and Vault Server 3.0.x

[williamstuart]

Hi,

I am using SourceGear Vault version 3.0.2.2812 on the server and a client with version 3.1.1.3506 and another one with a version of the 3.0 release. Also using Visual Studio 2005 Beta 2 and Visual Studio 2005 July 2005 CTP.

We added a Web Site project to an existing solution. The Web Site project was then added to the repository in SourceGear.

When compiling the solution or the web site project, there are error messages that pop up because the assemblies cannot be modified. The assemblies are in the Bin folder (and contrary to ASP.NET 1.1), the Bin folder is now visible inside the solution explorer. The bin folder has also been added to source control. So, checking out the Bin folder is a solution (the dlls can then be overwritten during compilation), but only one user at a time can do that, so that user is the only one who can compile the solution or the web project.

Has this issue been resolved with Vault Server 3.1? Is there an easy way to exclude that folder from source control?

Thanks,

William.

[lbauer]

With all these different client/server versions, it's hard to say what might be causing the problem.

I'd recommend upgrading clients and server to Vault 3.1. Then if you still experience the problem, it will be much easier to troubleshoot and reproduce, since we'll have eliminated the version variable.

[lbauer]

We did find this posting, which indicates the behavior you are seeing is most likely a bug in VS 2005:

http://lab.msdn.microsoft.com/ProductFe ... 4abc9c4005