Automatically connect using this profile disabled?
Moderator: SourceGear
-
- Posts: 42
- Joined: Mon Feb 16, 2004 6:10 am
Automatically connect using this profile disabled?
It seems that the setting to automatically connect using the selected profile is disabled in the VS client. Is there something in the 3.0.5 client that's changed from 2.0.6 on this point?
Regards,
Ralph Shillington
Regards,
Ralph Shillington
Automatically connect disabled
No, it does not automatically connect, it pops up that everlastingly annoying dialog every time
There might be a problem with your solution/project or mssccprj.scc file. See http://support.sourcegear.com/viewtopic.php?t=2474 for a desription of how to manually change the profile in each of your projects, and it should automatically connect after that.
I am using Vault ver 3.1.1 and i face the same problem. This is the content of MSSCCPRJ.SCC
This project was added by my collegue using her profile. When i get the latest version from the Vault Server and run it from the VS.Net IDE, the dialog appeared.
I don't face this problem with the projects i added in with my own profile.
What else should be done?
It shows the correct profile that i am using.SCC = This is a source code control file
[WinApp.csproj]
SCC_Aux_Path = http://csd-data-server/VaultService|Joel:4
SCC_Project_Name = $/C01-140-001(TieLine#2)
[WinApp.sln]
SCC_Aux_Path = http://csd-data-server/VaultService|Joel:4
SCC_Project_Name = $/C01-140-001(TieLine#2)
This project was added by my collegue using her profile. When i get the latest version from the Vault Server and run it from the VS.Net IDE, the dialog appeared.
I don't face this problem with the projects i added in with my own profile.
What else should be done?
Do you see these lines (with values other than SAK) in your project file (winapp.csproj)?
SccProjectName="SAK"
SccAuxPath="SAK"
SccLocalPath="SAK"
SccProvider="SAK"
I've personally found it easier to edit the sln and various project files by hand rather than try to get Visual Studio to do the right thing. It seems that if those Scc lines in the project say SAK, then the project uses the solution's source control settings, and then it is a matter of trying to get the correct information into the solution. It's all a big pain. Fortunately we don't add new projects all that often.
I know this may not help, I just thought I'd let you know that there seem to be several places that Visual Studio stores the source control path.
Mike
SccProjectName="SAK"
SccAuxPath="SAK"
SccLocalPath="SAK"
SccProvider="SAK"
I've personally found it easier to edit the sln and various project files by hand rather than try to get Visual Studio to do the right thing. It seems that if those Scc lines in the project say SAK, then the project uses the solution's source control settings, and then it is a matter of trying to get the correct information into the solution. It's all a big pain. Fortunately we don't add new projects all that often.
I know this may not help, I just thought I'd let you know that there seem to be several places that Visual Studio stores the source control path.
Mike