SourceGear Support

Can you describe your project structure? Do you have a solution file and other projects or is it just the web project?

I've reproduced this here and will look into it to see if it is a problem with Vault, or if the problem is Visual Studio not asking for files.

Yes, Create Blank Solution or Create New Project works best for adding new. The "right" way to get set up on a new machine is to first do an "Open From Source Control" from the IDE, which will set up working folders the way Visual Studio wants them. After that, a Get Latest from ...

The structure of a project is dictated by Visual Studio, which requires all projects to be underneath a common solution root if you are going to use source control integration. You can use any structure you want if you are using the Vault GUI client to manage source control operations. See this MS K...

Which modified date field are you referring to? The file list in Local View should show the local file system date, and the file list in Remote View should show the date of the last checked in version of the file. Note that Vault allows you to control the date the local file is set to on a Get: Eith...

It is likely that User B had not done a Get Latest prior to User A editing the file. If the file status is Old, and then it gets edited, it will have a Needs Merge status. The only way to avoid this is to have every user immediately do a Get Latest after each checkin by any other user. Or, in other ...

The status search pane in the Vault GUI client will list all the files that have a status of "Old" compared to your current working folder. You could do a Historical Get based on the last time you sent files to the client, and then search for all files that have changed since then, or just...

Does it still not load?

If you do an Open From Source Control from within Visual Studio, it changes your working folders to be where you told Visual Studio to put the files. So, be aware that there is an implied Set Working Folder that is part of the Open From Source Control operation.

OK, we've found the problem. gb2312.so actually depends on another encoding called gb_2312-80.so. So, you need to install the gb_2312-80.so file into the same inconv folder, and then gb2312 should load. It is in the attached file

Visual Studio integration doesn't work for a single solution spread across multiple repositories, due to limitations in the interface. So, you'll need to put them in the same repository if you want them to both work with SCC integration at the same time.

I dont see your logic as to why it could not be related to IIS. If there is a timeout problem in IIS, the local fast access wouldnt hit the problem and the remote users would hit the problem. Yes, that's true. Here are some more stabs in the dark on the IIS side: :) 1. Check the system event viewer...

If large files work fine for local users, but not for remote users, then the problem probably isn't IIS, but something between the remote users and IIS. If the problem were IIS, the local users should run into the same issues as remote users. Do you have firewall or VPN software that has either a ti...

I just tried a simple test with those conditions, and I got a "could not find label" error, so there must be other conditions that are causing this to happen. Is this a problem in the GUI client as well? If you do a show labels on $/ProjectA/SubcomponentB does the label show up? If you do ...

Are the versions just labels on the same Vault folder, or are they branched folders? If there are labels, then a history query between two dates will show you all the changes that have happened, which you can save as an HTML file as a report. If they are in different branches, you would need to do a...

Sorry, but there isn't currently a way to make all files mergable (although *.* was a good idea). I'll add this as a feature request though, as it seems like a reasonable thing to want to do. Note that when actual binary files get into a Needs Merge state, you won't really be able to merge them, sin...