Renegade Files

[btd]

Dear Vault:

We are on Vault 7.1 std edition.
In our Visual Studio project where Vault is the Source control, we have experienced this.

Form time to time Visual Studio 2012 will update files (like Nuget packages) but it does not check out the file BEFORE DURING or AFTER. This we end up with renegade files.

Do you know if there is something we can do to force Visual Studio 2012 to check out the files before updating them?

Thanks
Tom

[Beth]

When the files are updated, are they saved to your working folder with the changes and is Visual Studio open when this happens?

If the files are saved, then what happens if you go to File - Vault Source Control - Refresh Source Control Status? Do the files check out then?

Are your files set to read-only or writable? Auto-check out requires that the files be read-only.

One option you might consider is using CVS mode. That allows files to be edited without a check out, and then they are just listed as edited. From there you can just check them in.

There are some other articles around the internet that suggest not putting Nuget dlls into source control. Since we don't use Nuget here, I can't say which is the best route. The makers of Nuget would know better why some suggest that.

[btd]

What is CVS mode and how do I set this up for a test?

Thanks

[Beth]

Open Vault and go to Tools - Options - Concurrent Development Style. Click the CVS style button. You will see the options below it change.

Do you know if you are using the Vault Enhanced Client or the Vault Classic Client in Visual Studio? CVS mode is only an option for the Vault Enhanced Client. To check this, in VS go to Tools - Options - Source Control - Plug ins.