ReSharper 3.1 + VisualAssistX Problem in VS2008
(I accidentally originally posted this in the EAP forum. My apologies.)
I wanted to point out a very annoying performance problem that I've run into with VS2008.
I run with a combination of VisualAssistX (latest build) and the latest build of ReSharper 3.1. I love both tools, and rely on them both. I mainly use Visual Assist for its navigation bar feature, its type find feature, and most importantly, it's intellisense feature, which I find superior to the default and also to ReSharper's. Obviously, I run ReSharper with it configured to use Visual Studio's intellisense (Visual Assists).
I have run in this configuration for quite some time in VS2005 with no apparent problems.
After switching to VS2008, I noticed that my debugging single-step performance is incredibly slow. Each step in the debugger takes over a second, which is unacceptable to me.
If I disable both ReSharper and Visual Assist, debugging performance is normal (actually maybe even a little faster than in VS2005).
Interestingly, if I disable only Visual Assist (ReSharper enabled), or only disable ReSharper (Visual Assist enabled), then debugging performance is as good as when both are disabled.
This would lead me to conclude that there is some kind of interaction problem occurring in VS2008 when both Visual Assist and ReSharper are enabled.
Any ideas?
Thanks,
Jeremy
Please sign in to leave a comment.
Hello Jeremy,
1) What type of files the problem is observable in (i.e. is it C# files)?
2) Is it consistently observable?
3) Does it happen with a newly created solution?
Thanks.
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
This seems to be a problem with all types of files. I'm primarily working with C#, ASPX, ASCX, and XML files.
It is very consistently observable, even with a freshly started IDE, although the performance does appear to get worse as time passes (periodic IDE restarts are a fact of life with VS/ReSharper due to memory that slowly grows).
I haven't tried it with a fresh solution, but I will do so and report back to you.
Note that I accidentally originally posted in the EAP forum (again, sorry about that). In that thread, a user responded that he was having the same problems and indicated you guys were already working on the issue and a fix was imminent in 3.1.1. I hope that is the case.