SourceGear Support

I think I found the bug that causes this. I'll follow up when I know more.

Unfortunately Visual Studio's automation API only works with MSSCCI source control plugins. Your observation is correct, that only the Classic Client can be automated this way.

Thanks for the information.

If it's not too big a pain to get us the logs, I'd love to see what's going on for people reporting this problem. If you don't want to attach them here, you can email them to ian at sourcegear dot com.

The original poster asked if they could change the frequency or turn off that refresh, and we never answered that. You can.

In Visual Studio, this option is under Tools|Options|Source Control|Vault Options|Advanced Options.

The mutex timeouts when there are namespace conflicts was a known issue that was resolved in either 4.1.2 or 4.1.3. Can you upgrade your client to the latest version, 4.1.4? (It will work with any 4.1.x server, so you can upgrade the server whenever it's convenient.) If the behavior persists after u...

We definitely did underestimate the importance of this feature. Sorry about that. We didn't actually "take it out," however. Having this feature available in the new client is a matter of implementing it. We definitely understand now how useful and important this feature is to people, and ...

Thanks, that's a good suggestion.

The bad news is that a performance fix I made in 4.1.3 re-introduced this behavior.

The good news is that it's fixed in 4.1.4, which is now available.

Sorry for the inconvenience.

Your understanding is correct. There are a few scenarios where files outside the solution's structure can't be correctly handled correctly. The issue you're seeing with linked files is the result of a performance compromise. I still consider It a bug, but making it work and perform well is non-trivi...

Is the linked file beneath either a bound project or solution? If not, this is unfortunately a known issue.

(Bug 12318)

I'm unable to reproduce this behavior. Can I ask you to upgrade to the latest client (1.1.4)? This will work fine with your existing 1.1.x server. If the behavior persists, let us know.

What do you see when you try to check in a linked file?

We haven't determined the fix for this issue. The workarounds I listed are still the best option.

Thanks for the follow-up. Let us know if there's anything else we can do to help.