ReSharper 6.1 EAP Opens: Much More than a Bugfix Release

It took longer than expected but here we are, opening the ReSharper 6.1 Early Access Program that’s meant to eliminate any pain points you might be having with ReSharper 6.0, via performance and bug fixes. However, ReSharper 6.1 also provides a lot of new functionality that all 6.0 users will be getting as a free upgrade.

UPDATE! ReSharper 6.1 is officially released, Early Access Program is over.

Here are some of the best reasons why you should totally try ReSharper 6.1:

  • Performance fixes: Has ReSharper 6.0 been harsh on you performance-wise? Has it been processing source files longer than expected? 6.1 shouldn’t. Here’s the list of performance issues that have been fixed.
  • Bug fixes. The list of bugs fixed for 6.1 is here for you, highlighted by massive efforts to improve unit testing, structural search and replace, VB.NET code resolve, as well as code completion and typing assistance in ASP.NET MVC 3 (Razor).
  • New settings engine. Settings have been revamped extensively, with extra emphasis on sharing and managing them. We have made many more settings accessible and sharable, and introduced new granular settings — for example, those for IntelliSense behavior for different languages. Settings are now layered meaning that you can define global, per-solution, per-team or individual settings. You can now export and import all or selected settings to/from a single file — for this and other settings management operations, use the new Manage button under ReSharper > Options.

  • Here’s a rough list of settings-related problems solved for 6.1. Mind you, nothing is set in stone yet. We’re still making changes to this subsystem, and we’ll do that based on feedback from you and your team.

  • Support for Async CTP. You have asked for it: Not only does ReSharper 6.1 support async and await keywords — both in C# and VB.NET — but it also provides a set of code inspections and quick-fixes: for example, it sees dead code when an asynchronous method lacks await operators, and warns when you’re using a wrong return type in an asynchronous method.
  • Optimize Assembly References. This has been requested for even longer, and here it is: ReSharper 6.1 detects any references that are not effectively used in your project, and provides a nicely built UI to get rid of all or some of them. Project maintenance just got easier with ReSharper!
  • Experimental support for the initial Visual Studio 11 Developer Preview. We have adapted ReSharper to run under Dev11, and it does so fairly well with existing code. Manual setup is required here, and we’ll follow up with a post containing VS11 install guidelines. However, please understand that this is only initial, experimental support for existing types of projects with a specific Developer Preview build (the one made available on September 16, 2011.) We can’t guarantee any consistency of your experience with ReSharper 6.1 EAP (or even the future release of 6.1) under VS11 Developer Preview. Needless to say, no support for developing Metro style applications is there. Official support for VS11 will not be made available any earlier than the next major ReSharper release.
  • ReSharper SDK. This is something that should simplify ReSharper plug-in development dramatically. Delivered as an MSI or ZIP file, the SDK provides a full set of ReSharper assemblies, including test infrastructure assemblies required to test ReSharper plug-ins, target files, and (in the MSI version) Visual Studio templates for creating different kinds of plug-in projects.
  • A great load of improvements relevant to web developers. This includes new quick-fixes and refactorings for CSS; Structural Search and Replace for HTML and ASP.NET; Move Helper refactoring, internationalization and Call Tracking for ASP.NET MVC 3; generation of event subscriptions in ASP.NET; a UI to configure path mappings for web site deployment; and many more improvements, some major, others not so much, that we’ll be expanding upon in a separate blog post.
  • New code inspections and quick-fixes for C# and VB.NET. Aside from the set of Async CTP related inspections, ReSharper 6.1 has also improved in terms of control flow redundancy analysis (for instance, detecting more cases of redundant return statements); it also detects access to disposed closure and covariant array conversions, and provides corresponding quick-fixes where available.
  • XAML support improvements including code completion enhanced in certain scenarios, batch generation of event subscriptions, improved attached property awareness in error highlighting and code completion, as well as an option to create a namespace alias from usage:

We have also added a new refactoring to convert iterators to methods; internationalization for VB.NET projects; navigation and search updates including Quick Search in Type Hierarchy window, export to HTML and XML from all tool windows supporting import/export functionality; and more. There are simply too much changes, subtle and prominent, to summarize in a single blog post without turning it into an encyclopedia.

For die-hard fans, here’s the list of all YouTrack issues fixed for 6.1.

Go forward and download ReSharper 6.1 EAP builds ReSharper 6.1 official release, and expect more blog posts covering 6.1 functionality in greater detail to come up soon.

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

27 Responses to ReSharper 6.1 EAP Opens: Much More than a Bugfix Release

  1. Tom Robinson says:

    This sounds great – any idea if it’s compatible with the StyleCop for ReSharper plug-in?

  2. Dennis says:

    Ahhhhh, sooo much nicer. Before it could take 1 min to type something in a razor file… Now it is down to a more reasonable 2 seconds again.
    It still feels slughish, but much much better than 6.0 RTM.

    I can see some new razor parser errors though…

    @section js {

    @{@:$(document).ready(function() {
    gives a warning on the last paranthese.

  3. Bob says:

    Sorry for being so clueless but I’m not sure how to install. I ran the MSI successfully but R# still reports itself as being version 6.0.2202.688 in VS. Is this by design or are there additional steps I have to take to complete the install? Thanks.

  4. Paul den Boer says:

    I’m getting the same problem as Bob. I installed 6.1 over 6.0, then opened VS2010 and it 6.0 is still active. I uninstalled 6.0 and repair installed 6.1. Now I don’t have ReSharper in VS at all.

  5. @Tom No, StyleCop 4.6 shouldn’t work with 6.1 yet. It’s early EAP, so you shouldn’t generally count on plug-ins to work with it at this time. I know that the MSpec plug-in is being updated to support 6.1, and xUnit plug-in as well. As to other plug-ins, this will require some time for them to catch up.

  6. @Dennis
    Can you please report the parser bug to ReSharper issue tracker please? If you happen to catch substantial performance issues, please report them there, too. Thanks!

  7. @Bob, @Paul This is weird and not a known problem.
    Can I give your e-mail contacts to our QA guy so that we’re all able to reproduce/diagnose this problem?

    @Everyone Is anyone aside of Bob and Paul experiencing installation issues?

  8. Slava.Trenogin says:

    @Dennis, I can’t reproduce this. All green for me.
    Can you create a small repro project?

  9. Dennis says:

    created as 278549

  10. Andrew Gibson says:

    Any progress on the QUnit (or Jasmine) integration? e.g. still unable to reference javascript files unless they are sitting beside the tests….

  11. @Andrew
    Can you provide a link to the corresponding issue in YouTrack please?

  12. Hadi says:

    Not sure how to enable this for VS2011, but it seem to need a manual configuration and the installer has no option for VS2011. Anything I am missing?

  13. Laurence says:

    Those who mentioned they installed 6.1 but still shows 6. You probably downloaded the SDK without realising, double check what you downloaded and installed in add/remove programs. Resharper itself is actually the top link in the download, the bottom zip/msi are for the SDK, I made this same mistake myself.

  14. Paul says:

    Can someone from Jetbrains explain us how to enable 6.1 for VS11, please?

  15. Øystein Krog says:

    Agreed, would love to test it in Visual Studio 11, please post the instructions for manual install:)

  16. Thanh Dang says:

    Make sure that you download correct Resharper 6.1 EAP installation file, that is around 54MB in size, not the SDK package. If still fail, you should try remove old 6.0 and then install fresh 6.1.

  17. Craig Dean says:


    I ALSO installed the SDK rather than ReSharper itself, I’d suggest changing the ReSharper link in the download section to ReSharper (.msi) – it kind of looks like a heading.

    I admit – it’s me being careless, but if these comments are anything to go by I’m not the only blind idiot on here x)

  18. Allan Michaelsen says:

    I would also like to have an install guide for VS11…

  19. Jon Kragh says:

    Great work! Definite speed improvements on my machine with the latest 6.1 build.

    I’m new to resharper but it seems that when running an MS Unit test via resharper that the App.config does not get copied / read when running a test. I can run the same test under MS Test, and my test can read the app.config ok.

    Should I open a bug for the 6.1 EAP around this, or are there other steps that are usually taken for resharper to copy app.config files for unit tests?


  20. @Hadi, @Paul, @Øystein, @Allan
    Sorry for a delay with the guidelines. We thought, we’d publish a VSIX installer instead. Please see the fresh drop to the EAP page and download the VSIX.

  21. Alex says:

    Async CTP and Optimize usage?
    DO WANT!

    btw, we posponed Async usage in silverlight project due ReSharper was nt able to handle that, and everyone on the team give me “that look”, if they want to write it without resharper support :D

  22. Charles W. Hooks says:

    Is the out of virtual memory problem fixed for x86 machines?

  23. @Charles
    Possibly. Need to know how the problem has been reported (bug report to the issue tracker, support request etc.) to provide a definite answer.

  24. Jack says:

    hi, when 6.1 will it release?

  25. @Jack
    We’re looking to release a beta sometime in December, then we’ll need a few more weeks to prepare the final build.

  26. Ian says:

    Is there any chance that will get done in 6.1?

    Can Optimize Assembly References detect references that are only used by a using statement?

    A replace for add project reference that explains the cycle would also be nice; managing references on a large old project is a big pain!

  27. @Ian No chance unfortunately since ReSharper 6.1 was released yesterday

    Assemblies only used in using statements are detected as efficiently unused, yes.

    As to a replacement to “Add reference > project”, can you further elaborate on that? What would you like to see?

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> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>