Post
by gmagana » Wed Nov 23, 2005 12:08 pm
Thanks for the suggestions. I checked out the logs as you mentioned (I also turned on "debugging" loggin for Vault). There was no mention by either the Vault log or the VS SCC log of even a checkout attempt when there clearly should have been one (editing of a checked-in file).
What I did then was remove the SCC bidings from the solution, save the solution, exit VS. Then restart VS, load the (non-SCC bound) solution, and rebind everything in the solution to the appropriate Vault locations. VS got latest (at least I think that's what it was doing...), and I was warned about local files being different than the SCC server versions. I chose to not change any local files whenever prompted.
Then I exited VS again, and through the Vault client, checked-in the new renegade files (I think all were project files) to Vault.
One strange note was that the only difference in these project files had from the existing ones was what seemed like data corruption at the very beginning, all had three non-ASCII bytes inserted at the very beginning of the file, and that was the only change... Very very strange...
Anyway, it seems to be working now. I tried to edit about 50 different files (one at a time, of course!) and, without exception, VS correctly did a check-out for all, so I am a very happy person right now!
As to the changes that fixed it, maybe it will remain a VS2005 secret, because the physical file changes of unbinding and re-binding the solution and its projects were very hard to see/detect.
gabriel magana-gonzalez