Vault keeps adding files back...

Post by **jclausius** » Mon Oct 15, 2007 8:05 am

neal007 wrote:One detail I failed to mentioned, these projects are asp.net web site projects.

OK. I was using a Console Based project. Give me some time today to test a ASP.NET web site project.

Post by **jclausius** » Mon Oct 15, 2007 10:54 am

Neal:

I was able to recreate this. Here are my findings. As of Vault 4.0.4, the MSSCCI based client does not perform repository deletions of files removed from the repository. The option on GET to remove a file from the working folder has been disabled, and cannot be configured for the VS2003 Compatible client.

For non-web site based projects this works out because the project files remove the file from within Visual Studio (although the file is left in the working folder). However, web site solutions do not contain any project file, it uses all files found in the directory. Since the Vault client is leaving the file in the working folder, the other users are seeing the file on disk being added back via Pending Checkin.

Note, this is not a problem with the Visual Studio 2005 IDE client, as of Vault 4.0.4 this client always removes the file from the working folder.

This is not what we want to see in the VS 2003 Compatible client, so I've logged a high priority bug to fix this in an later release of Vault 4.0.x. Sorry you had to run into this the hard way, but you have my gratitude for the report.

neal007 · Post by **neal007** » Mon Oct 15, 2007 11:03 am

Thank you for pinning down the issue Jeff! Can we use "mixed" source code control, i.e. our solutions have multiple class libraries and one web app. Can we bind the web app using the Vault 2005 client and leave the other projects with the Vault 2003 client or is it all or nothing?

I hope this can be fixed in the 4.0.5 release, otherwise we are going to have to change our Vault binding which I really don't want to do as these projects are shared in other solutions as well.

Post by **jclausius** » Mon Oct 15, 2007 12:27 pm

Neal:

The fix will most likely be in Vault 4.0.6 (as most likely there will be news about Vault 4.0.5 in a matter of days). However, this will be one of the first things fixed in that version.

As for what to do right now, within Visual Studio 2005 you can have multiple solutions/projects bound to different version control providers. So having a mixed solution environment (where each solution/project is bound to one) should work at that level. Be forewarned, I've never experimented where shared projects within different solution have different bindings, so I don't know what to expect with that cofiguration.

neal007 · Post by **neal007** » Fri Oct 19, 2007 9:22 am

Jeff,

Anothing thing I noticed is Vault is like a Dyson!!! It picks up any new files in the folder structure and adds them in on its own. For example - I use Developer Express controls and they released an update. I use their project converter to upgrade the project with the new assembly refs, etc. It makes .BAK files of the files it updates. Open VS.NET after this and the web project adds all these delightful .bak files into Vault just because they are there!

FYI

Post by **jclausius** » Fri Oct 19, 2007 1:21 pm

The way Microsoft designed Visual Studio 2005 was to instruct the MSSCCI client for web projects to add ANY new files/folders found in the directory to the pending change set. I don't know if we can code around that behavior. Nonetheless, it is good information to have, and I'll add that to the bug to see if anything can be done.

One possible work-around... I'm not 100% certain, but I think there is a MS add-on which allows for a PROJECT file to control the web site. If this is true, you could modify your existing solution use this, as the project file would then stop any unnecessary files/folders from being added.