RE: Extract (from Vault), Include in Project (from VS), Vault checks out the file...
"Eric Sink" <[email protected]>
| Newsgroups | gmane.comp.version-control.sourcegear-vault.user |
|---|---|
| Message-ID | <[email protected]> |
I don't think there's a setting which corresponds to this behavior. It does indeed sound "hokey" though. Are you sure the file is actually checked out? I think Visual Studio shows a file as checked out whenever it is under source control and writable. Perhaps the problem is that the file is simply still writable? -- Eric Sink Software Craftsman http://software.ericsink.com/ -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Monte Kalisch Sent: Friday, January 30, 2004 3:08 PM To: [email protected] Subject: [vault-list] Extract (from Vault), Include in Project (from VS), Vault checks out the file... Using Vault 1.2.3, if I extract a new file (that's not in my project) to disk, and then go into my project and Show/Hide all files (refresh from disk), I can see that the new file isn't in my project (grey'd out). Since my project file itself is not read-only, I should just be able to right-click on the file in question and "Include in Project." That does work and VS makes the appropriate modifications to the project file. The problem is that somewhere along the way the file I'm "including" gets checked out (and I didn't ask for that to happen). Is there a setting for this because it doesn't seem like that should happen. I can work around it by undoing the check-out and reverting the file back, but it's hokey. =) TIA! _______________________________________________ vault-list mailing list [email protected] http://lists.sourcegear.com/cgi-bin/mailman/listinfo/vault-list