DevPinoy.org
A Filipino Developers Community

>>> First two to make 3 wins! <<<

Problematic Resharper 3.0 Beta

The beta release of Resharper 3.0 seems to be very buggy for me.  First, it was the double Resharper menus with my visual studio installation.  Second, I experienced the control+left and control+right shortcuts not working.  Third, is the buggy Resharper settings page throwing unhandled exceptions.  I wouldn't recommend installing it.  The stable EAP release I think is better.


Posted 06-01-2007 4:48 PM by jokiz
Filed under:

Comments

jokiz wrote Resharper 3.0 Beta is out
on 06-01-2007 12:57 AM

Jetbrains has just released their beta version of Resharper 3.0, download it here . Again, VB.NET guys

Avery wrote re: Problematic Resharper 3.0 Beta
on 06-01-2007 10:46 AM

I had 2.5 installed and installed 3.0 Beta over it. It broke my intellisense :( I can't get visual studio or resharper intellisense working now. Really disappointed. Oh well, back to 2.5.

Tony Merante wrote re: Problematic Resharper 3.0 Beta
on 06-02-2007 9:25 AM

Yea I'm experiencing some of the same problems. For the double resharper menu, You have uninstall all resharper versions and then run dev.exe /setup from a command. then install resharper 3.0... Of course that will reset any custom visual studio hotkeys you have set up.

jokiz wrote re: Problematic Resharper 3.0 Beta
on 06-04-2007 3:51 AM

tony, the workaround proposed by jetbrains i think is better for the double resharper menu

Kevin wrote re: Problematic Resharper 3.0 Beta
on 07-31-2007 6:53 AM

even in the release version of 3.0, I found it painfully slow on vb.net.

Crache wrote re: Problematic Resharper 3.0 Beta
on 09-05-2007 8:35 PM

Under Visual Studio 2005 .NET, to get IntelliSense to work again if Resharper broke it, you can go into the \Common7\IDE\ directory and run "devenv.exe /ResetSettings" to reset VS back to defaults.  If you have a lot of custom settings, maybe you can look at a way to backup the important ones, but this made IntelliSense usable again.

There may be a more direct way to solve the problem without resetting everything, but I've never tried Resharper and haven't had this problem myself, so you're on your own.


Copyright DevPinoy 2005-2008