#Visual assist x vs resharper c++ install
#Visual assist x vs resharper c++ full

I'd like to provide some additional information that may be helpful. 0 and the latest release of ReSharper 3.1. I am using Visual Studio 2008 with Visual Assist X. I have seen the same performance problems. Howdy, I'd also like to chime in on this topic. Let me know if there's any other information I can provide which would be helpful. Many thanks for investigating this - as an additional datapoint, I tried turning off all Resharper's intellisense and extra syntax colouring (I prefer VA's implementation of all that anyway), and that didn't seem to make much/any difference. I have installed ReSharper for VS2005 onto a separate test machine for reference, and while I am seeing CPU spikes there, they are smaller and a lot shorter, so the problems are considerably worse in VS2008, at least for me.

My CPU is spending a lot of time stuck at 100% in VS2008, there is definitely something going on here. There is a different download for VS2008. Zen is the art of being at one with the two'ness We have other users who use both VA and ReSharper at the same time without the problems you are reporting, so it would make sense if the problem is related to VS2008. VS2008 RTM made some changes from the last beta and this caused VA problems. It is possible ReSharper does not fully support VS2008 yet.

#Visual assist x vs resharper c++ full

'JetBrains ReSharper 3.0 Full Edition can only be installed on machines with Visual Studio 8.0 installed.'

#Visual assist x vs resharper c++ install

I have just downloaded the Resharper 3.02 trial and I am trying to install it on my VS2008 test machine, and I have just received the following error message: Has anyone else had any success getting these two products to behave together, at least slightly? Could WT improve the 'disable for specific languages' behaviour?

Disabled VA in the Tools->Add-ons dialog - this fixed the problem, but of course it's a pain if I want to do a little C++ work. Disabled VA on the VisualAssist menu - this had no effect either.ДЈ. This didn't seem to make any difference - the VA dlls still appear in all the procmon traces.Дў. I suspect getting VA and RS to share an editor window nicely is probably impossible, but it would be nice if the products could rub-along a little closer, so to this end I tried the following:ДЎ. Using ProcMon (which can look back up a call-stack) suggests that VA is repeatedly looking-up stuff (like VS colors) in the registry when repainting the editor window. My experience of having them both installed is that the C# editor becomes utterly unusably slow - even task-switching to VS has a several second delay associated with it. I'm a 100% loyal 8-10 years VisualAssist user, but I thought I'd try out Resharper recently, knowing that it does more clever C# stuff than VA does. Whole Tomato Software Forums - Resharper again, sorry