SourceGear Support

I've never had a problem with the Vault Client. It's only inside the IDE that we have issues.

Versions are...
[08/25/2008 2:48:04 PM] Version Check: This Vault client is version 4.1.2.18185
[08/25/2008 2:48:04 PM] Version Check: Your Vault server is version 4.1.2.18185

We'be start intermitantly getting NullReference type exceptions with the VSIP client in Visual Studio 2005. It seems to start happening when the VSIP client tries to "update" the status of all the files in the project. Unfortunately it seems to do it once for each file in the solution and ...

Hey Jeremy, I just figured this out. If I changed the devenv.exe.config to match the vaultguiclient.exe.config the issue dissapears. I believe it has something to do with specifiying the <proxy usesystemdefeault="true" /> element. My guess is that the old Visual Studio client doesn't use t...

Ever since we upgraded to 4.1.0 and started using the vault VSIP client we've been having some really frustrating issues with the Visual Studio integration. Not sure if they're related or not but here we go. The first issue is when we attempt to do a checkin with some adds and edits. Half the time t...

Plain old Gui seems to work fine. I'll get the occasional dropped connection - maybe once an hour. With the IDE though I'll get those error messages every second vault interaction. It's extremely consistant, which is odd, but extremely frustrating too...

Hey Jeremy, I disabled Keep Alives on the server - didn't seem to accomplish much. I've had the IDE log running for a couple days and I have some more information available. Here's the log... 3/26/2008 8:20:27 AM <generic>: [Main:2572] GetEntryAssembly() returned null; not logging assembly name 3/26...

In the Vault Gui I occasionally get a message about a connection that should have been kept alive was closed. I turned on logging and the only info I got in the VaultIDEClient was this... 3/26/2008 8:20:27 AM <generic>: [Main:2572] GetEntryAssembly() returned null; not logging assembly name Nothing ...

Hey Jeremy, turning that flag on or off doesn't seem to make a difference.

Chris

One of the features we use in vault is the ability to connect to our server from offsite whenever we need a change of atmosphere from the office. Ever since we upgraded to 4.1 our access offsite has gone somewhat screwy. Whenever we make an action inside of Visual Studio that would require a vault c...

We did have ASPNET installed. Once I added Default.aspx it worked fine, and its's possible that the machine had default.aspx removed - it just caused a bit of confusion this morning when I had to troubleshoot why I couldn't get onto the admin webpage.

Chris

I think the default webpage for the Admin folder might be screwed up on the Server Install. The shortcut it creates points to http://myVaultServer/vaultservice/admin but there is no default webpage setup on that guy. I've attached a screen snap of the "default documents" for that folder. I...

Thanks - managed to figure it out based on those sample. I was using the saveSession parameter on vaultsetloginoptions incorrectly.

So on 3.5.1 of Vault we use to use this nant snipit to label our project after every successful build on our build server... <vaultlabel repository="Evolution" path="${RepositoryFolderPath}" labelstring="${version}" username="SomeUser" password="SomePassw...

I can't say for sure how it worked before 3.5 - I didn't really pay attention but for some reason I thought that even the prompt when creating a new solution from Vault was skipped if you had a default profile selected. I'm not really sure though so it's not too big a deal.

We're currently running vault version 3.5 and a small problem I have occurs when you're using Visual Studio 2005 and you choose to Open a Project from source control. The vault "Connect to Server" dialog box pops-up on top of visual studio. Life's good, I'm opening 5 other apps at the same...