Vault 3.0.5 and VS.NET 2003 binding issues

[axinom]

1. Is it known bug that in the "Change Source Control" dialog of VS.NET the column "Server Binding" always shows "Unable to display"? When do you plan to fix it?

2. Since the abovementioned dialog is nearly useless we are trying to check or to change bindings manually. Is it somewhere described where Vault stores and how Vault manages the binding information? We've found parts of binding information in the solution file, project files and files MSSCCPRJ.SCC and <projectname>.vspscc.

3. Our solutions have normally 6 to 15 projects, 3 to 5 of them are web projects. We make a branch every time we release (every two weeks). Fixing all bindings manually after each branch is laborous. Can you propose any automatic or semiautomatic workaround to the bindings problem?

4. When we branch a project the solution and visual studio project files are copied to the new branch folder. As far as we understand they contain wrong binding information. What is recommended way to get branched version to an empty workstation without getting files from the trunk? Is it possible without using Vault Client?

Thank you.

[dan]

1. Is it known bug that in the "Change Source Control" dialog of VS.NET the column "Server Binding" always shows "Unable to display"? When do you plan to fix it?

Yes, this is a known bug, and we hope to have it addressed in either 3.1 or 4.0

2. Since the abovementioned dialog is nearly useless we are trying to check or to change bindings manually. Is it somewhere described where Vault stores and how Vault manages the binding information? We've found parts of binding information in the solution file, project files and files MSSCCPRJ.SCC and <projectname>.vspscc.

All of Vault-specific info is in MSSCCPRJ.SCC, but VS stores SCC info in project/solution files and elsewhere, depending on the version of VS. However, to see which working folder is associated with which Vault folder, look in the MSSCCPRJ.SCC files.

3. Our solutions have normally 6 to 15 projects, 3 to 5 of them are web projects. We make a branch every time we release (every two weeks). Fixing all bindings manually after each branch is laborous. Can you propose any automatic or semiautomatic workaround to the bindings problem?

4. When we branch a project the solution and visual studio project files are copied to the new branch folder. As far as we understand they contain wrong binding information. What is recommended way to get branched version to an empty workstation without getting files from the trunk? Is it possible without using Vault Client?

You might start with some KB articles at:
http://support.sourcegear.com/viewtopic.php?t=1917 and
http://support.sourcegear.com/viewtopic.php?t=194

I don't believe anyone has come up with an automated solution for this yet.

Thanks,