ReSharper 8.0.1 EAP is Open

Nothing is perfect, including ReSharper 8.0. After a month of usage, there’s a more or less clear picture of issues and regressions that should be addressed in a bugfix update for 8.0. Since many of the issues that have surfaced are already fixed, ReSharper 8.0.1 Early Access is now available and includes 60+ fixes.

The list of fixes made this far covers unit testing first and foremost (freezes, crashes, incorrect status after running tests), followed by UI fixes including those for the new License Information dialog box. Other fixed issues include settings that couldn’t be exported in 8.0, and code analysis regressions such as second check expression in a double-check lock reported as always true (RSRP-358572).

If a problem that is bugging you with ReSharper 8.0 is already fixed, please download ReSharper 8.0.1 EAP and help us verify that it has indeed gone away.

Note that we’re looking to fix 50 more issues before releasing 8.0.1, and they will be addressed in subsequent 8.0.1 EAP builds.

This entry was posted in News and Events and tagged , . Bookmark the permalink.

6 Responses to ReSharper 8.0.1 EAP is Open

  1. Todd says:

    Good to see the commitment to fix this release. I am disappointed in the quality of 8.0 and its clear that with about 110 fixes on the plate for the first maintenance release there was a real QA issue here. So the one fix I really hope you look at is how you address these quality issues going forward.

  2. Geoff says:

    Agreed. It seemed like the beta for R# 8 was very short. I used the last beta before it RTM’d and it felt very beta. The performance was so much worse than 7 that I had to go back to 7 really quickly. Will give the next release another shot but my confidence in the product has taken a hit.

  3. Sam Gentile says:

    I also had to back and/or go to another product. The performance is abysmal. This is both to startup with no project or to startup and work in a medium size Bootstrap/MVC project. I posted on Twitter, “Well something’s got to be done. Even with SSD Resharper/VS12 takes 32 sec to open and a whopping 176 sec to open MVC/BS sol” This is W/o Resharper 8 VS12 takes 8 sec to load and 36 sec for the Bootstrap/MVC program!

    I need to know part of these fixes are performance related and if not I’ll have to start looking at another vendor like JustCode.

  4. @Sam Thanks for reporting but there’s no guarantee that the current 8.0.1 build is any better. We have one pending issue related to Bootstrap MVC but it might very well be different from yours.
    In order to judge what’s causing this extraordinary slowness and remove the problem, the best way is for you to profile Visual Studio and provide us performance snapshots for investigation. This is very simple: you can choose ‘ReSharper | Help | Profile Visual Studio’. This action will start profiling immediately: as soon as you’ve recorded a representative snapshot, press ‘Get Snapshot’, and follow the instructions for sending the snapshot to JetBrains FTP server. In your particular case, we’d appreciate if you send two performance snapshots our way: one representing the 32 seconds required to open Visual Studio, and another representing opening the BS/MVC solution.
    Thanks!

  5. Nolan says:

    Looked through the bug fixes and saw that the Unit Test Runner was going to now support Microsoft.Fakes. However, I still get “UnitTestIsolation instrumentation failed to initialize. Please restart Visual Studio and rerun this test” when I try to run tests in R#. Tests work using MS Test Runner.

  6. @Nolan
    I believe that the problem you’re talking about is described in this bug report.
    The problem is unfortunately not going to be fixed in 8.0.1 but it’s scheduled for 8.1 that is expected later this year.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">