RE: Binding web solution.
"Eric Sink" <[email protected]>
| Newsgroups | gmane.comp.version-control.sourcegear-vault.user |
|---|---|
| Message-ID | <[email protected]> |
In the past, when it appears that "Vault keeps resetting the working directories of projects rather than leave them to inherited", what's really going on is that the working directories at every level had been previously set for some reason and those settings are still lying around. In this case, the easy way out is the old "delete your client cache files" trick: cd %appdata% cd sourcegear cd vault_1 cd client cd (big long hex string) cd (your Vault user name) dir you should see several files that start with CacheMember. del CacheMember_* -- Eric Sink Software Craftsman http://software.ericsink.com/ -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Monday, January 12, 2004 1:42 PM To: [email protected] Subject: [vault-list] Binding web solution. I have a solution with 2 web projects (asp.net) and a dll. On new machine I am having trouble binding the projects again. It appears that if you install everything initially, the open through source control works (still few issues with binding of web apps). But if there is an error (framework 1.1 somehow lost security rights) and have to reinstall framework, vault or visual studios throws an error with open through source control. My workaround is to rebind. Rebinding works for everything except solution, in which it keeps saying the working directory is "c:\". Too, vault keeps resetting the working directories of projects rather than leave them to "inherited". Any ideas on how to rebind solution? --------------------------- Clayton Dool Application Developer, Axium 503.350.2156 [email protected] _______________________________________________ vault-list mailing list [email protected] http://lists.sourcegear.com/cgi-bin/mailman/listinfo/vault-list