SourceGear Support

Yes, that fix is in 4.0.6. Project1 contains a VS2005 project with a sample.resx file; This compiles in VS 2005. Project1Branch contains the BRANCHED version of Project1, opened with VS2008 (open from source) and originally able to compile after the VS 2008 conversion wizard ran. Next, I made a CHA...

We've reproduced this bug, and will have a fix for it in 4.0.6. If you need a fix sooner, please email me using the button below this post. Did the fix for this problem make it into 4.0.6? I just encountered a similar problem doing a merge of a VS 2005 .xml RESOURCE file into a VS 2008 project tree...

But note that in another thread has been reported as a bug and will be fixed.

The installation guide at http://www.sourcegear.com/vault/support/install4.html refers to 'serverinstall.html', but this file does not exist. Reference: A Vault Home web page will also be created. To access this page, you should go to http://<vaultservername>/VaultService/serverinstall.html. This pa...

If I start over, with a new repository, I won't have the data that has been built up in the old repository for the last 4 years. The idea was to import the OLD source that we left in VSS 4 years ago when we started using vault with the intent to import it over later when 'we had time' and the import...

Due to stupidity, we tried to import the rest of our VSS database into vault on a SQLEXPRESS system. Of course it ran into the 4GB upper limit. Sigh. If I restore the vault database as of the last backup (taken DURING the import process, about 1/2 way through before it started to fail due to databas...

We branched our project using 3.5.2 (5087) from Head to x.x I then opened the x.x from source control using VS 2005. It appeared to work; however, I later discovered that my 'working' folders in Vault were constantly being reset incorrectly in the Head tree to the x.x tree. After reviewing the sourc...

I am in the process of upgrading our development projects from VS 2003 to VS 2005 (using Team System 'Demo' version at moment). I first tried opening the Solution file from the location on my local disk where Vault's working directory is set. The VS 2005 conversion program started its wizard, warned...

The display area for the working folder: line in vault client is limited in size to where very long pathnames no longer show up to completion, even when you make the vault client application size large (two display screens worth). There is still lots of white space, but the text for the pathname is ...

My last experiment was to go simply into VS2005, checkout 1 source file located in a project within a solution, UNDO the checkout and quit VS2005. Checking in vault, the working folder for both the Project folder, and the Solution folder were set to the 'MSNET2005' variant. I reset the solution fold...

Above testing was done on vault 3.1.0 (3494)

Similar problem, but VS2005 CHANGES working directory Keith Dorken, 2005-08-19 I am experimenting running VS2003 and VS2005 on the same machine, with VAULT. I set the working directory for VS2003 to C:\MSNET I open VS2003; my source control bindings are correct (they were bound to C:\MSNET) I close ...

The upgrade went without any problems whatsoever. The only 'change' we have noticed is a occasional request to 'login' to the vault server and pick a repository after a session has timed out overnight.

This isn't the best, but it does keep the vault history of the files around. 1) In the vault client, share the files to the new location you want them to be. 2) Get the files to the new location. 3) In the IDE, EXCLUDE the files from the project in the old location 4) In the IDE, INCLUDE EXISTING FI...

I processed the upgrade to vault 3.0 serial number exchange back in december in anticipation of upgrading over the holidays and printed the result on the printer. I didn't notice until now (of course) that when you print the output with the new serial number on it on 8 1/2 x 11 portrait format that ...