SourceGear Support

Indeed, that will work. Sorry for the inconvenience.

We hope to handle layouts like these better in a future release.
(Bug 13281)

I'm glad to hear that fixed it.

We do hope to make the performance ramifications of thousands of pending changes less severe in a future release.
(Bug 13769)

Sorry you've having trouble.

Are you saying this worked in 4.1.1 but doesn't work in 4.1.3?

Does the information from this post apply?

It looks like we're spending a fair amount of time sorting through your pending changes to determine those changes that apply to the currently open solution. When you open the stand-alone client, (apporixmately) how many pending changes are listed? In Visual Studio, with this solution open, how many...

This shouldn't be possible. If you can reproduce the problem, I'd like to see the Visual Studio enhanced client logs, in particular for the second user who's editing when another user has the file checked out. Information about turning on the log and finding the file can be found here . Follow the d...

Unfortunately the log doesn't have anything particularly revealing. Can you reproduce this every time now, just by doing a get latest? Would you mind posting a screenshot of your Local Files options? In Visual Studio, you can get there via Tools->Options->Source Control->Fortress Options->Advanced O...

You're welcome. Let us know if there's anything else we can do to help.

These articles from the FAQ may be helpful, particularly if you're using the Visual Studio Enhanced Client:

• My project files constantly get checked out exclusively, which is a real pain. What’s the deal?
• What's the story on mergeable file types?

The enhanced client doesn't automatically prompt to retrieve projects, as you've seen. You can enable always get latest when opening a solution, if that's helpful.

The Vault Classic Client may provide this option--it looks and feels more like VSS.

Those messages are posted to Visual Studio's output pane. There's more info in the FAQ.

I'd suggest having the external users add an alias to their hosts file to resolve the internal name to the address that works for them. (Or vice versa, depending on which would affect fewer developers.)

Unfortunately your workflow isn't anticipated by the current binding design. You can do it, but there is an extra step outside Visual Studio. I wondered if the reason for the failure was that we should add the source code to SourceGear before making the bindings. However, I only see the option to &q...

A Refresh Source Control Status (under File->Fortress Source Control) inside Visual Studio will update the pending changes pane to reflect changes made outside Visual Studio. If this is something you need to do often, you can set a keyboard shortcut or make the Fortress Enhanced Client toolbar visib...

We were able to reproduce this, and it's not specific to VS.PHP projects. When a project is in the root folder of a drive, its files' repository paths aren't correctly determined. (In the test I posted yesterday, I had a working folder mapped to a drive root, but didn't have a project in the drive r...

It probably doesn't matter, but just in case: are you using VS 2005 or 2008?