This weekend, we essentially renamed our vault server and upgraded the OS to Windows Server 2003. The server upgrade went very well--thanks, Jeff! And updating profiles for the Vault client worked without a hitch.
Our Visual Studio 2003 ASP.NET project, however, has something odd in it. First off, if users change the name of their Vault profile--as I did--then every time you open Visual Studio, it complains about a bad username or password. This is not really the problem; it's just complaining.
So if you rename the profile back to what it was, you stop getting this prompting. I notice this is consistent with what was reported on the forums <a href="http://support.sourcegear.com/viewtopic ... er+binding" target="_blank">elsewhere</a>.
There is something that concerns me, though, and that's that Visual Studio still thinks the bindings are incorrect. If I File > Source Control > Change Source Control, I can see that it's still referencing the old server name and profile in there.
I saw <a href="http://support.sourcegear.com/viewtopic.php?t=2474" target="_blank">this post</a> which suggested changing the information in the MSSCCPRJ.SCC file, but I don't think that is correct. First off, I did change it and Visual Studio completely ignored it. I suspect the real binding information is stored in binary in the .SUO file. I think this SCC file is just a copy. If you don't believe me, change the file, open Visual Studio, see that the information is still incorrect in the bindings. I even read on the <a href="http://support.microsoft.com/?id=147585" target="_blank">Microsoft site</a> that the file is only used by Visual Basic (we're using C#). You can even delete this file completely and reopen Visual Studio and it will just be recreated.
So that brings me to the real question. How do I change the bindings in Visual Studio? If I go into the Change Source Control option above and unbind the project, it removes the source control details from my local version, but when I go back in to rebind it as was suggested on <a href="http://support.sourcegear.com/viewtopic ... bc0944e4ad" target="_blank">this page</a>, it looks like it wants to RE-ADD the entire thing to Vault. It's already there and I'm scared of screwing up our entire project by proceeding here.
Any thoughts?
Oh - I do note that we can just delete all versions of the project locally and refetch it from Vault. Then, things are fine. But we have some folks who can't just get all latest because they have files open and in progress.
Renamed Vault server; now VS 2003 ASP.NET bindings are off
Moderator: SourceGear
If there are concerns about what Visual Studio would say about it, you could perform a fresh open from source control. Those who have changes to upload yet will want to save a copy of their work somewhere out of the way. If after the fresh open they can't get their changes merged in or their files are overwritten, then there are two ways they can approach this.
1) Make sure the file that needs changes uploaded is checked out. Close VS and Vault. Overwrite the file in the working directly with the one with changes, then open Vault or VS and check it in.
2) Change the Vault concurrent development settings to CVS. Close VS and Vault. Overwrite the file in the working directly with the one with changes, then open Vault and that file will be sitting in the pending check-ins now because Vault can see changes were made. It can be checked in then. I don't believe CVS style will work with Visual Studio though.
1) Make sure the file that needs changes uploaded is checked out. Close VS and Vault. Overwrite the file in the working directly with the one with changes, then open Vault or VS and check it in.
2) Change the Vault concurrent development settings to CVS. Close VS and Vault. Overwrite the file in the working directly with the one with changes, then open Vault and that file will be sitting in the pending check-ins now because Vault can see changes were made. It can be checked in then. I don't believe CVS style will work with Visual Studio though.
Last edited by Beth on Mon Jan 29, 2007 4:03 pm, edited 1 time in total.
So basically what you're telling me is that the methods suggested in the other posts do not work to fix this issue? And truly the only way is to re-fetch the project from Source Control? I just want to be sure that's it. It seems like there should be some way to detach/attach a project without re-fetching it, but I certainly haven't been successful in my attempts either. Sad.
Thank you for helping though.
Thank you for helping though.
No, the methods you read and what you were doing will work. You could just continue forward with what you were doing and it should be fine. It's just been with my experience and the various things that users will do that often it's easier to just perform a fresh open from source control, because then one doesn't have to worry about what VS will have to say about it. Sorry if I gave the impression that others were wrong. I will edit my post.