SourceGear Support

Ok, I found a way to do it in the GUI.

The history query dialog has an option that says, "View folder history by version." (The default is "by item.")

That view allows selection of the top level $/ by virtually any date via the "Get Tree" button. Works great.

Hello, I need to do some analysis on historical versions of our repository. I found this topic from just a few days ago: http://support.sourcegear.com/viewtopic.php?t=9119&highlight=get+past+date Just ike that person, I do not have labels on the dates I need them. I tried the method described in...

Ok, discovering the File->Source Control->Change Source Control dialog was educational. In retrospect, I should have started there. That's where the old server was defined. Unfortunately, I was unable to "re-bind" the projects. After unbinding from the old server (which is still running) a...

I'm just going to create a new solution file from scratch and download the project from Vault. That seems to have fixed the issue. I no longer get the protocol error, and my profile is automatically selected. Am I going to have to recreate all dozen of my Vault projects? Knowing that the issue is p...

I removed the SUO file, and VS recreated it. But VS won't open the project from the old location. See screenshot.

I'm just going to create a new solution file from scratch and download the project from Vault.

Well, I found one file with a reference to Server X: the .SUO hidden file that's in the solution directory. I think it is a binary file? Opening it in notepad, I can see a line with Server X in it. I made a backup copy and attempted to edit the file. I changed the reference from Server X to Y. Openi...

Ok, I setup logging and found references to the old server. I'll post the log file below. However, I cannot find any SCC files that reference the old server. If it's in the log, it's got to be in some configuration file somewhere, right? I looked at both MSSCCPRJ.SCC and <projectname>.csproj.vspscc,...

Well, yes, I would like to use a profile to connect. Again, here's what happens: Upon starting VS.NET, my default profile is not selected and the checkbox "Automatically connect..." is disabled. I can choose the profile from the drop down list and connect with it, but the same thing happen...

(this was a duplicate post... sorry)

When I open a solution in Visual Studio 2003, I get an error message: "This Vault server uses a protocol that is not supported by this client." I'm running Vault 3.0.6 on both the client and server. I've triple-checked it :D When I click OK, the "Connect To Server" dialog does no...