SourceGear Support

whew - I'm glad to hear that

I was not able to reproduce this, so there must be some other steps required to get this to happen.

If you go to a second machine, or login as a different user, do the obliterated items still appear?

If you start with a fresh repository, can you reproduce the steps as you've outlined them below?

The steps you outlined should work, and I wasn't able to reproduce it on a simple database.

What version of Vault are you using, and is there anything else about the folders you sharing into (or the files themselves) that make them non-standard?

It should be available in June.

3.5 is an interim release, meant to indicate it isn't quite 4.0, but is much more than a 3.2.

Yes, this does appear to be a problem with Web Projects. We'll take a look, but I'm not sure how much we will be able to do about it. It looks like Visual Studio automatically adds files that exist in the web folder as pending additions.

Vault 3.5 will have the ability to add folders from the Vault main window, by turning on an option that will show local folders in the main tree.

By File List, are you referring to the file list in the Vault GUI client, or the file list in the Dreamweaver client? Can you post a screenshot so we can see exactly what you are seeing? A Get Latest in the Vault GUI client with the Set File Time set to "Check In" should set the local file...

It looks like a SQL Server hiccup. Hopefully it won't be an issue again.

I was able to reproduce this, but it seems to only happen when the Get Latest is done after the file is deleted but before the project file is checked in. Note that deleting a file in Visual Studio 2005 is a two step process - deleting the file will immediately delete it in source control, but it al...

The logs indicate the client is having trouble downloading the repository structure, which in this user's case is a compressed file. IIS 6 on Win2K3 sometimes will send a different session token to our client on a very fast download. The Vault client interprets this as an invalid session, and bombs ...

Was this after an upgrade or some other configuration change on the machine?

And, does it happen everytime you login, or just that one time?

Check the server log for the server you are logging into and see whether it has a more useful message.

In what way was the shared folder out of sync?

Was the shared folder shared more than one time, and if so, which share link did you delete?

Dan, you might also want to enable client logging and see where the slowdown seems to be.

Are either of you using the 2.0 framework on the client side, and is the client in a different timezone from the server? An issue recently cropped up with that configuration that caused slowdowns.

Workgroup edition will work fine with Vault, but any limitations with that version of SQL will apply to Vault DB as well (such as a 3GB RAM limit for the DB).

Take a look at the label command help. You can apply a label to a folder, then do a Show Labels later, select the label, and get the folder tree as it existed at the time of the label. If the purpose of creating a new folder for a tree and copying files there is just to have a historical record and ...