RE: Disconnected Checkout - Best practices?
"Eric Sink" <[email protected]>
| Newsgroups | gmane.comp.version-control.sourcegear-vault.user |
|---|---|
| Message-ID | <[email protected]> |
I assume you're talking about the Work Offline feature in Visual Studio. We don't have any set of best practices for using this particular feature. If you can give us some more specific information about the problem you're having, we might able to help. BTW, the best way to work disconnected is to use our so-called "CVS Mode". Unfortunately, this way of working is supported only in the main Vault client, not within Visual Studio. In this "mode", Vault doesn't require files to be checked out before you edit them. It automatically notices your changes and places them in your pending change set as if you had checked them out. We sometimes call this "CVS mode" since it implements the "edit-merge-commit" model of development which is similar to the way CVS works. Anyway, this is a great way to do development when you're not connected to the server. -- Eric Sink Software Craftsman http://software.ericsink.com/ -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Josh Robinson Sent: Monday, January 05, 2004 6:35 AM To: [email protected] Subject: [vault-list] Disconnected Checkout - Best practices? We use Vault 1.2.2 for our small dev team here at work. It is a huge improvement from the constant frustrations that we faced with VSS over the years. However, I have lately become so frustrated with the Disconnected Checkout (or Work Offline?) feature as to find it unusable and can no longer feel confident that any work I perform over the weekend will make it into my source control at the office. It is likely that I am doing something wrong, so rather than give gory details about each step that I am doing (which I will gladly do), I would love for someone (at SourceGear or otherwise) to run through the steps that are required in a disconnected check-out scenario. Then, (and this is the critical part) what are the steps to properly re-connect to the Vault on Monday morning without losing all your inspired weekend code. That is the weak link for me right now, I keep losing everything when I come in on monday morning. I hate to say it, but never had trouble with this feature of VSS, so I'm sure that I'm just doing it wrong with Vault. Thanks for any help! Josh