I am running 5.0.4 Vault with VS2010. Whenever I try to exclude a file or files from a project that is under Vault source control, the files are deleted out of the file folder where they reside on the hard drive as well as from the project listing. Looking at the Vault pending changes tab I see the files are marked for deletion from Vault. I have to undo the pending changes so that I get the files back in the file folder. This has caused me some problems and I was wondering if SourceGear was aware of this problem and what the fix is for it?
For some reason Vault see's and exclude as a call for deletion which it should not.
VS 2010 Exclude file(s) get deleted with Vault
Moderator: SourceGear
Re: VS 2010 Exclude file(s) get deleted with Vault
You are correct. We have a bug logged on this. Sorry for the inconvenience. You are currently doing the right thing by not automatically committing your deletes. If you accidentally delete something, it can be recovered again. Just right-click the parent folder in Vault, select Properties, and go to the Delete Items tab. There you can restore deleted files.
Do you have to exclude items from Vault often? Are those files that are added during the Add to Source Control or are they added some other way?
F: 15477
Do you have to exclude items from Vault often? Are those files that are added during the Add to Source Control or are they added some other way?
F: 15477
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
Re: VS 2010 Exclude file(s) get deleted with Vault
4 years later and apparently this issue has not been fixed.
Re: VS 2010 Exclude file(s) get deleted with Vault
This bug was first reported 8 months ago and refers to a problem where a delete removes it from a working folder in VS 2010. It appears earlier versions of VS did not display this behavior.joniba wrote:4 years later and apparently this issue has not been fixed.
In any case I will be looking at this in Vault 6.
Jeff Clausius
SourceGear
SourceGear
Re: VS 2010 Exclude file(s) get deleted with Vault
Vault Standard and Vault Professional 5.1.2 address this issue.
Jeff Clausius
SourceGear
SourceGear