Vault "touching" file in checkin

[el veejay]

It seems like vault is "touching" files (giving them a new modified timestamp) on checkin, which is extremely annoying, as Visual Studio then wants to reload everything.

How can I tell vault NOT to do that?

[Beth]

Are the files edited? Vault has to look at the files to determine changes. If there are files you don't plan on editing, then an Undo Check Out will be performed on the files.

[el veejay]

No it doesn't edit the files (or at least there's no visible change), but it makes Visual Studio think someone else edited the files, which means that VS will want to reload the files in question. I hope there's some config thing I need to turn off (or on).

[Beth]

Are you adding the files through Visual Studio or through the Vault GUI client?

Are you wanting to use the integration between VS and Vault? That allows you to use Vault actions inside of VS.

[el veejay]

I have the Vault plugin, so when I create a new file, it gets added automatically. However, I check in from the standalone Vault client, as my checkins usually spans several VS solutions. And after I do, VS claims the files have been modified.

[Beth]

There's a couple different things that could cause what you are seeing. The easiest way around that is to turn on CRC checks. That's in the Vault Tools - Options - Local Files.

The other options are to look at how working folders are set. It's possible to have a conflict there by both setting a working folder in Vault, and then Binding with VS at a different level.

Or, you can perform all your check ins inside of Visual Studio.