Here is a link to the bug report that I made to Microsoft:
https://connect.microsoft.com/VisualStu ... r-from-ide
Here is a link to a video I made reproducing the error, and demonstrating the relationship to SourceGear Vault Professional
http://www.screencast.com/t/3JIfd1zA
This issue appears to be unique to SourceGear. The manifestation of these errors depends on whether the document is opened before or after checkout from Vault.
Vault Pro with VS 2010 results in "Invalid Pointer"
Re: Vault Pro with VS 2010 results in "Invalid Pointer"
Update....
This issue depends on the Fortress "Make writable" option under "Local Files".
If it is set to "Make all files read-only", then the problem manifests. If it is set to "Make binary files read-only", then the issue does not manifest.
This issue depends on the Fortress "Make writable" option under "Local Files".
If it is set to "Make all files read-only", then the problem manifests. If it is set to "Make binary files read-only", then the issue does not manifest.
Re: Vault Pro with VS 2010 results in "Invalid Pointer"
Thanks for the information and update. We'll see if we can reproduce it here and log a bug.
bug: 15961
bug: 15961
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Re: Vault Pro with VS 2010 results in "Invalid Pointer"
Thanks... I was also too hasty in my second reply. Changing the "writeable" flag doesn't fix the issue. Once I check a file in, the issue manifests on the file if I try to check it out and do any more edits. I have to close, checkout, and then re-open the file.