Hi,
Since upgrading to vault 3.1.5, I keep getting the dialog box to select my repostory. I've only one repository and it is set as default in my profile. I've also deleted and created a new profile since the upgrade. It also keeps asking me to log in every time I want to check in/out a new project. I thought once you've logged into the client, it should be seamless and not request re-logins? I'm using VS.NET 2003.
Thanks
Repository Dialog box
Moderator: SourceGear
We've had one other report of this, but we've not yet been able to figure out why it is happening. A possible work-around is to replace the values in following lines in the project file with "SAK" instead of the binding info:
SccProjectName="SAK"
SccAuxPath="SAK"
SccLocalPath="SAK"
SccProvider="SAK"
However, you might try to turn on client logging and send it to us before doing this, as we might be able to see what VS is sending us that is causing the problem. See http://support.sourcegear.com/viewtopic.php?t=2898 for how to do that.
SccProjectName="SAK"
SccAuxPath="SAK"
SccLocalPath="SAK"
SccProvider="SAK"
However, you might try to turn on client logging and send it to us before doing this, as we might be able to see what VS is sending us that is causing the problem. See http://support.sourcegear.com/viewtopic.php?t=2898 for how to do that.
The other user who reported this turned on logging, and it was revealed that Visual Studio was not sending Vault any information about the server and repository to connect to (or the profile to use).
We did make one change in the 3.1.1 timeframe that forces the Choose Repository dialog to be displayed if the repository sent to us from VS is invalid. It might be that the solution/project in question never had the right binding info, but this was only revealed after the Vault upgrade, and it was just using the values that had previously been used when connecting via the GUI client.
In any case, rebinding should fix the problem.
We did make one change in the 3.1.1 timeframe that forces the Choose Repository dialog to be displayed if the repository sent to us from VS is invalid. It might be that the solution/project in question never had the right binding info, but this was only revealed after the Vault upgrade, and it was just using the values that had previously been used when connecting via the GUI client.
In any case, rebinding should fix the problem.
Hi, how do I re-bind. Is it by following the procedure to add the SAK line?dan wrote:The other user who reported this turned on logging, and it was revealed that Visual Studio was not sending Vault any information about the server and repository to connect to (or the profile to use).
We did make one change in the 3.1.1 timeframe that forces the Choose Repository dialog to be displayed if the repository sent to us from VS is invalid. It might be that the solution/project in question never had the right binding info, but this was only revealed after the Vault upgrade, and it was just using the values that had previously been used when connecting via the GUI client.
In any case, rebinding should fix the problem.
Do I ammend it on the MSSCCPRJ.SCC file? Would it have the same effect if I was to delete this file and then get vault to recreate by opening the project from source control?Paulm wrote:Hi, how do I re-bind. Is it by following the procedure to add the SAK line?dan wrote:The other user who reported this turned on logging, and it was revealed that Visual Studio was not sending Vault any information about the server and repository to connect to (or the profile to use).
We did make one change in the 3.1.1 timeframe that forces the Choose Repository dialog to be displayed if the repository sent to us from VS is invalid. It might be that the solution/project in question never had the right binding info, but this was only revealed after the Vault upgrade, and it was just using the values that had previously been used when connecting via the GUI client.
In any case, rebinding should fix the problem.
Thanks