How to check out MSSCCPRJ.SCC

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
uanmi
Posts: 13
Joined: Thu May 12, 2005 10:16 pm

How to check out MSSCCPRJ.SCC

Post by uanmi » Sun Mar 05, 2006 4:17 am

I have done a branch and have now read with horror the poor support in Vault for this activity. What can I say but this really is a very poor aspect of Vault and should be fixed.

Why did we buy Vault? So that things like branch would work. I could do the same hacking in VSS and I would not have had to buy Vault.

Not happy
thank you
Mark Gregory

dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Post by dan » Sun Mar 05, 2006 3:04 pm

Sorry for the frustration, but this is a Visual Studio issue, not a Vault issue.

It is related to how VS stores its binding information, and will exist for any source control tool.

uanmi
Posts: 13
Joined: Thu May 12, 2005 10:16 pm

Branch

Post by uanmi » Sun Mar 05, 2006 3:49 pm

No, I would expect Vault to have an option "Branch and fix VS paths"
You have known about this issue for many years and you could have done this.

You have nothing in the online help about the problem. How many years have you known about it? You could have warned VS users that there is a problem but have chosen not to. I consider this really dumb.

I am not impressed with your lack of customer focus.
thank you
Mark Gregory

dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Post by dan » Sun Mar 05, 2006 9:22 pm

Again, sorry for your frustration, but it generally isn't helpful to insult us about a Visual Studio problem while we are providing support on a weekend.

uanmi
Posts: 13
Joined: Thu May 12, 2005 10:16 pm

Branching

Post by uanmi » Sun Mar 05, 2006 10:17 pm

Your product should be able to overcome the problem, when I do a branch in Vault client it effectively copies all the files from one folder to the next. It is pretty obvious that someone will have to update the paths in the files. When I did the branch visual studio was not even open, it was not part of the problem, just Vault. Vault needed to correct the paths, they have changed in the branch just as they would in any source control application that includes branch capability.

What I'm saying is that you do not mention this in the help, you do not have a guide to fix, and you have not provided a tool to do what is pretty straight forward and is part of the step your client should have when doing a branch.

It is too late to find out about this after you do a branch. If you cannot see that it is dumb for every new user of Vault to have the same problem and be looking for the same fix then I can only say that Sourcegear needs to consider a customer focus.
thank you
Mark Gregory

Post Reply