This is not a Vault question, per se, but hopefully someone will know...
Does anyone know if VBW files should be stored in source control? I have an elaborate multi-project application that I open a group file. Even if I don't make any edits, Vault reports that all of the VBW files for each project have changed. I suspect (by peeking into the file) that the file simply contains info on window positions and are the same as the "user" files in the .NET IDEs, and would probably be okay to remove from source control, but I don't want to break anything.
Anyone know if it's okay to remove these files from source control?
VB6 VBW Files
Moderator: SourceGear