Hello, running 3.5.3.5169 on the client and 3.5.2.5087 on the server. My project is in VS2003.
When I try to bind the project to Vault, click either the Bind button or Browse button (in case it's already bound, but needs rebinding elsewhere), it literally takes about 1-2 minutes to actually display the browse dialog. Then when the browse dialog is actually displayed, expanding tree nodes is really weird: the expanded nodes are not displayed (empty space), unless you use the keyboard to navigate there.
All this is happening in a Windows XP SP2, which is run inside a Microsoft Virtual PC 2007.
Help please.
Why is Vault so slow with VS2003?
Moderator: SourceGear
Re: Why is Vault so slow with VS2003?
Virtual machines have been found to cause a lot of slow-down. Are any other functions slow or only the binding?
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
Re: Why is Vault so slow with VS2003?
Only binding is slow. Everything else is fine. That's the weird part.
And how would a virtual machine cause such a massive slowdown? It makes no sense.
And how would a virtual machine cause such a massive slowdown? It makes no sense.
Re: Why is Vault so slow with VS2003?
Problem resolved. After trying various things with Sourcegear Tech Support, it turns out that Resharper 2.0 and Vault 3.5.x do not play well together. I turned off Resharper and the binding operation is massively fast again.
Regards and thanks to Beth.
Regards and thanks to Beth.
Re: Why is Vault so slow with VS2003?
Thanks for the update. That's good information to know.
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support