SourceGear Support

To follow up on this note: We just release Vault 3.1.9 today that addresses the problem of files being automatically added back to web projects after a Get. Note that you have to do a Get Latest Recursive on the project (Gets on individual files will not trigger the fix).

Vault 3.1.9 is now available

See http://support.sourcegear.com/viewtopic.php?t=6244 for more info.

As suspected, there isn't anything we can do about this - it is a Visual Studio dialog, and is managed from within VS. You'll need to go to the MS Visual Studio forums and request the functionality there.

3.1.9 is a maintance release for 3.1. If you have not upgraded to any 3.1 Vault version, see http://support.sourcegear.com/viewtopic.php?t=4294 for more information. The following changes are included in this release: GUI Client Only - Get Latest will no longer delete local files if a repository fol...

After digging around some more without luck, Brian eventually re-created the project file outside of source control, checked it in, then opened from source control and re-binded the project in Change Source Control. After that, everything seemed to work fine.

Take a look at this KB article: http://support.sourcegear.com/viewtopic.php?t=1014. It has a lot of good things to try for timeout issues.

Step 7 is still in the "Create local project from Vault" dialog where you select the folder in Folder that contains the .dtproj file. There is a text box labelled "Create new project in working folder:", that allows you to change the working folder for the dtproj. Make sure that ...

OK, I need to be able to reproduce this here to see what is going on. Here's what I did: 1. Created a new sample SSIS project and added a few .dtsx files to it. 2. Added the new project to source control 3. Exited and re-invoked VS 4. Created a new blank solution in a new working folder 5. Went to S...

The working folder info is stored in the client cache on the local machine, in docs & settings.

Trying it on a different machine would help determine whether the problem is related to the project itself, or with the user account/state or machine configuration.

I followed these steps on a sample SSIS project, and it seemed to work fine. Is the working folder defined in Vault for the user name who did the Add From SCC where you expect it to be? You might try this from as a different user or from a different machine and see if the problem is related to a use...

I believe the install folder for MX2004 is C:\Program Files\Common Files\Macromedia\2004\SourceControl, so first make sure the Vault_DWIDE.dll file exists there. If you go (in Dreamweaver) to Manage Sites, Edit Site, go to the Advanced tab, and select Remote info, is SourceGear Vault listed in the A...

Ah, sorry to not read that carefully enough. It looks like the working folder for $/FSA_Legacy/Database/Migration/Data Migration is E:\BCISOURCE\FSA_Legacy\Database\Migration\Data Migration. Is this path accessible to the local client? If you tried to manually create Upload.pif there, would you be a...

It looks like E:\BCISOURCE\FSA_Legacy\Database\Migration\Data Migration\Upload.pif is currently open or being accessed by another process. Do you have another program running that would have this file open?

Generally, once you connect to a repository during a VS session, it will reconnect to the same one, so you have to exit VS and then re-enter it to connect to a different one. Hopefully this is only an issue when doing one time operations such as Open from Source Control or Add To Source Control.

The problem is probably the -destpath argument. This specifies a non working folder to get the files to, and does not update the file state. If you already have a working folder defined, you don't need to specify where the files should go - it will put them in the working folder automatically. Also,...