RE: Project (and solution) Binding Behavior that drives me nuts
"Dan Schreiber" <[email protected]> Thu, 19 Aug 2004 22:47:57 -0500
| Newsgroups | gmane.comp.version-control.sourcegear-vault.user |
|---|---|
| Message-ID | <[email protected]> |
Chris, In Vault, you need to do an Open From Source Control from within VS to = get the initial binding. After that, Gets from the IDE should work as = expected. -Dan > -----Original Message----- > From: [email protected] > [mailto:[email protected]]On Behalf Of Chris = Mullins > Sent: Thursday, August 19, 2004 5:30 PM > To: [email protected] > Subject: [vault-list] Project (and solution) Binding Behavior that > drives me nuts >=20 >=20 > 1. create a project, save it, and check it into Vault (using=20 > VS.NET Integration).=20 > 2. Delete the local project (and all related directories) > 3. Get Latest from Vault > 4. Open project > 5. Click ok "Binding Error" that comes up.=20 > 6. File | Change Soruce Control | Bind Proejct > 7. Start making changes > =20 > Why do steps 5 and 6 happen? This is probably single issue with=20 > Vault that I (and other developers) have. We're constantly having=20 > to rebind proejcts when we get latest from source control.=20 > =20 > Using SourceSafe, this works cleanly. Using Vault is really gets=20 > in the way. Especially on very large projects.=20 > =20 > Is there a work around for this?=20 > =20 > --=20 > Chris Mullins >=20