Deployment project, merge modules want to go into Vault

[erict]

I need to add the Crystal Merge modules to my deployment project, because they're not detected as a dependency. Now VS.NET insists that these MSMs should be included in Vault; since they're off a different root directory, VS.NET gets mighty snooty about it. How can I convince VS.NET that this file should be included, but not into Vault? (If I click Remove, I take it right out of the project...)

Thanks,
Eric T.

[dan]

Try File->Source Control->Exclude file from Source Control. This doesn't actually remove it from Vault, but it does prevent it from being checked out or in.

The general answer though is that Visual Studio controls all this, and Vault just does what it is told to by VS...