VS2003 1 solution, 3 projects, loads of logins
Moderator: SourceGear
VS2003 1 solution, 3 projects, loads of logins
Hi I am using 3.0.6 of the free version integrated into VS2003.
I have an issue with the number of times I'm asked to login to the server to start work on a solution.
Example: I have all solution with 3 projects (2 winform and 1 web based). If I open the project from the start page Vault will ask me to login. I change profiles and put in the password.
As far as I'm concerned I've authenticated against the server for that solution but Vault asks me over and over again for my password on average 3 times per project I have in the solution. Why?
Surely, I either authenticate or I don't so if I do the first time, why does it need me to keep authenticating?
Since I've started using Vault I find I'm less inclined to switch working on solutions (which personally I do a lot) as it takes so long.
Thanks
I have an issue with the number of times I'm asked to login to the server to start work on a solution.
Example: I have all solution with 3 projects (2 winform and 1 web based). If I open the project from the start page Vault will ask me to login. I change profiles and put in the password.
As far as I'm concerned I've authenticated against the server for that solution but Vault asks me over and over again for my password on average 3 times per project I have in the solution. Why?
Surely, I either authenticate or I don't so if I do the first time, why does it need me to keep authenticating?
Since I've started using Vault I find I'm less inclined to switch working on solutions (which personally I do a lot) as it takes so long.
Thanks
This is not normal behavior - Vault usually only asks to login once, and then uses the connection info again.
Try going into Change Source Control and see whether it believes you are connected. You might try disconnecting and then connecting again from that dialog and see if it resets.
The underlying issue is probably that the MSSCCPRJ.SCC file doesn't have the correct info in it. See http://support.sourcegear.com/viewtopic.php?t=2474 for how to manually change those files (there is one per project folder) to contain the correct connection info.
Try going into Change Source Control and see whether it believes you are connected. You might try disconnecting and then connecting again from that dialog and see if it resets.
The underlying issue is probably that the MSSCCPRJ.SCC file doesn't have the correct info in it. See http://support.sourcegear.com/viewtopic.php?t=2474 for how to manually change those files (there is one per project folder) to contain the correct connection info.
Thanks for the reply.
I tried it yesterday. I changed all 3 .scc files in the solution to use the profile I needed at that time and it connected and the Get dialog launched after only 1 login as you would expect and hope.
Now, today I'm in the other location I work from and would need the other profile to get access to the Vault server than is currently set in the .scc files due to me manually changing them yesterday.
Like I said, this is just a solution with 3 projects. I had to login in 8 times before the Get screen displayed!
These aren't login failure, retry but simply having to present my credentials multiple times.
Having to change the .scc files manually everytime is a bit ridiculous.
I tried it yesterday. I changed all 3 .scc files in the solution to use the profile I needed at that time and it connected and the Get dialog launched after only 1 login as you would expect and hope.
Now, today I'm in the other location I work from and would need the other profile to get access to the Vault server than is currently set in the .scc files due to me manually changing them yesterday.
Like I said, this is just a solution with 3 projects. I had to login in 8 times before the Get screen displayed!
These aren't login failure, retry but simply having to present my credentials multiple times.
Having to change the .scc files manually everytime is a bit ridiculous.
How is the connection info different from your other location? Aren't you connecting to the same server and repository?
I'm not sure why it keeps asking you to login - it is likely that Visual Studio sees that the binding information is different and keeps sending us requests to login with the new information. However, if you can make the connection info the same, it would avoid the problem.
I'm not sure why it keeps asking you to login - it is likely that Visual Studio sees that the binding information is different and keeps sending us requests to login with the new information. However, if you can make the connection info the same, it would avoid the problem.
The server and repository are the same.
The differences are from one profile I work from within the same network as the vault server so I use its actual IP address (or machine name).
The other location is outside the LAN and I am not VPNing in but tunnelling direct through the firewall and then it's being natted to the vault box. So in this case I need to use the IP of the firewall's red interface which is obviously different.
The differences are from one profile I work from within the same network as the vault server so I use its actual IP address (or machine name).
The other location is outside the LAN and I am not VPNing in but tunnelling direct through the firewall and then it's being natted to the vault box. So in this case I need to use the IP of the firewall's red interface which is obviously different.