SourceGear Support

Sounds good. I already got 3.0.1 running on my server, but I'm sure that there are other people who will appreciate your efforts. (-:

Vault is awesome, a smooth install process will make it even better!

Keep up the good work, guys.

Josh

You guys are awesome! 12-hour turnaround on a weekend!

The DLL fixed it, so I'm happy. (-:

Josh

I just finished upgrading from 2.0.5 to 3.0.1, and I am getting the error "An error occured when you attempted to access the source control system. Check Installation." when I try to open a solution in the IDE. In this thread , Dan said that this is a known issue, and that you have a test ...

I chose the DOMAIN\MACHINE$ option when I upgraded to Vault 3.0.1, but the Vault Web Service kept throwing errors about being unable to access the directories under Temporary ASP.NET files. Finally, I figured out that I had to give the NETWORK SERVICE account full control over the directory, in addi...

My company mostly uses the default options in the Vault client, but we do have a few that are different. Is there any way to automatically update everybody's machine to use the same set of options?

We're using 2.0.5, but we're probably upgrading to 3.0 this weekend.

There is an option in the Vault client to Undo Checkout on unchanged files, instead of checking them in. That way, you can just check in the whole set, and it will only do it to the modified ones.

When I checkin multiple files through the Visual Studio integration, my comments are applied to each individual file, and the change set comment is blank. It seems to me that the change set comment should also be the comment that I entered. Just a thought...

Josh

Oh, ok. I have no idea how that happened...

Just ignore me, then. (-:

Yes.

I checked a file in with a comment that contained a comma. When I view the file's history, the comment is displayed as just a single comma. However, if I view that version's details, the whole comment is displayed. The server is running 2.0.5, and my client is 2.0.6. Not a big deal, just thought I'd...

I just upgraded my Vault client from 2.0.5 to 2.0.6, and it went smoothly, except for one thing. At one point in the install, there was a checkbox to make Vault the default source control provider. I did not check it, because Vault was already the default provider. The next time I opened Visual Stud...

I didn't see it in Tools, but I did find it in the View menu. However, it just loads the web client. That's OK, except that it makes me log in again, which is annoying.

Obviously, this isn't a big problem, I'm just being an annoying customer.

I really like the "Blame" feature in the web client interface. However, I can't find it in the Vault Client program. Is it unique to the web client? If it is, when do you think the Vault Client will get it?

Thanks!
Josh

Here you go. One thing that it could be (I just realized this - I'm stupid) is that we're running VSS 2005 on that box (from another test). Here's the log, in case you want to research it, but I'm just going to try it again w/ 6.0c. ---------------------------------------------------------------- Op...

I am evaluating Vault, and it looks pretty cool! However, when I try to import a VSS database, I get a weird error (see attached images). Any idea what's going on?

Note: I attached the screenshots in the wrong order - prescan.jpg is first, then error.jpg.

Thanks,
Josh Yeager