If you are having a problem using Vault, post a message here.
Moderator: SourceGear
-
petergjones
- Posts: 7
- Joined: Thu May 06, 2004 9:54 pm
Post
by petergjones » Mon Jun 14, 2004 6:02 pm
Whenever I view/change source control bindings in VS.Net, the dialog always displays <unable to display>. This makes it very difficult to see what the binding is - especially when branching!
-
dan
- Posts: 2448
- Joined: Wed Dec 17, 2003 5:03 pm
- Location: SourceGear
-
Contact:
Post
by dan » Mon Jun 14, 2004 9:48 pm
Thanks for the feedback. I think a few other people have noticed this too, and we'll look into it.
-
cdaniel
- Posts: 27
- Joined: Mon Jun 07, 2004 12:07 pm
- Location: Serious Magic
Post
by cdaniel » Tue Jun 15, 2004 12:45 pm
Yep! We've definitely noticed that too. In fact, I've never seen binding information in VS for any SCM product other than VSS!
-cd
-
dan
- Posts: 2448
- Joined: Wed Dec 17, 2003 5:03 pm
- Location: SourceGear
-
Contact:
Post
by dan » Tue Jun 15, 2004 1:13 pm
One thing to note is that you can get the connection information from the MSSCCPRJ.SCC files (one per project). Although certainly not as convenient as seeing them in the binding dialog, there is a place where a human can read them
-
petergjones
- Posts: 7
- Joined: Thu May 06, 2004 9:54 pm
Post
by petergjones » Wed Jun 16, 2004 5:18 pm
Should these files be checked in ? When I migrated I found that I had to delete these files and the VSSCC ones or VS.Net got completely confused about bindings.
-
dan
- Posts: 2448
- Joined: Wed Dec 17, 2003 5:03 pm
- Location: SourceGear
-
Contact:
Post
by dan » Wed Jun 16, 2004 8:25 pm
They should definitely not be checked in - they contain connection information about the project that can vary slightly for each user, and as you noticed, cause bindings to become invalid.