RE: Project (and solution) Binding Behavior that drives me nuts

We've been doing that for some time now.=20

Unfortunately it doesn't always work though. We store all our solutions
in a single "solutions" directory, and each time we do this "open from
source control" it wipes out the contents of that directory.=20

This process over a slow connection (even DSL, with SSL or VPN) is
agonizing for large projects. It also means that it's very difficult for
remote developers to wipe the local source code cache, and start fresh.=20

--=20
Chris Mullins

-----Original Message-----
From: Dan Schreiber [mailto:[email protected]]=20
Sent: Thursday, August 19, 2004 8:48 PM
To: Chris Mullins; [email protected]
Subject: RE: [vault-list] Project (and solution) Binding Behavior that
drives me nuts

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