Meanwhile… ReSharper 10 EAP kicks off

We have just opened Early Access Program for ReSharper 10, which means you can start using the latest development builds of ReSharper and its sibling tools: ReSharper C++, dotTrace, dotCover, dotPeek and dotMemory.

We should note that we’re not starting with a bang this time: a lot of changes, large and small, that we expect to make part of this release are not merged in yet, and we’ll be making more announcements as they are introduced in the EAP. In addition, as of the inaugural EAP build, noticeable changes have only occurred in the mainline ReSharper, and all the other products are only available for compatibility purposes.

That said, here’s a couple of reasons why you might want to try ReSharper 10 EAP right now:

  • Initial support for JSX syntax is now available in .jsx files order to streamline using React in ASP.NET applications. Code completion, all ReSharper’s regular context actions for HTML and JavaScript, navigation to declarations and search for usages, as well as a couple of refactorings are already available:
    Refactoring options as part of JSX support in ReSharper
  • JavaScript regular expressions that were originally supported in ReSharper 9.2 are now covered in more detail. Specifically, regular expressions are now recognized in RegExp constructors and methods, as well as in String object methods (match(), search(), replace(), split()), in addition to regular expression literals. Also, Make regular expression and Remove regular expression context actions are now available in JavaScript.
    JavaScript regular expressions via RegExp objects
  • TypeScript 1.6 support has gotten stronger with the addition of intersection types (RSRP-445826).
  • Less red code in C#. We’ve fixed a number of scenarios where ReSharper couldn’t resolve perfectly valid code, such as extension methods (RSRP-447688), System references in Xamarin.Forms projects (RSRP-447755), and await statements in Universal Windows Platform applications (RSRP-445975). Web sites in Visual Studio 2015 have received their fair share of red code fixes as well.
  • Fixes in ReSharper Command Line Tools, mostly related to analyzing WPF applications (RSRP-447361) and making sure that InspectCode can be successfully launched on funny file paths (RSRP-447873).
  • IntelliSense fixes related to formatting on completion before attribute (RSRP-437539), smart completion formerly leading to Visual Studio errors (RSRP-445914), and performance issues when collecting extension methods to show in completion (RSRP-447262).
  • An important unit testing regression has been fixed, and parent nodes in Unit Test Sessions tool window again show exactly how many child tests have failed (RSRP-442851).

If you find the changes outlined above relevant to your work, please download ReSharper 10 EAP, and expect more changes soon: both in ReSharper itself and in other products that are part of the ReSharper Ultimate family.

This entry was posted in How-To's and tagged , , , , , . Bookmark the permalink.

18 Responses to Meanwhile… ReSharper 10 EAP kicks off

  1. Matthijs ter Woord says:

    Keep up the great work!

    Can we expect improved support for Shared Projects (VS 2015) as well? (code generation, specifically, ie, generating classes/interfaces/etc from the solution explorer)

    • Jura Gorohovsky says:

      Thanks Matthijs

      AFAIK we’re trying to fix problems with shared projects in a routine fashion, as we get to know about them. You can see the status of issues related to shared projects using this link.

  2. LordJZ says:

    Wow that was fast. Most critical TS issues fixed — good job, thanks!

  3. Pingback: Dew Drop – September 15, 2015 (#2090) | Morning Dew

  4. Pingback: ReSharper 10 EAP, Mobile Shopping & Python 3.5

  5. Calin says:

    You guys are the best.

  6. Alex says:

    Is JSX support only available in JSX files?

    • Jura Gorohovsky says:

      Yes, as mentioned in the post, it’s limited to .jsx files so far. This will hopefully change in further EAP builds.

  7. Pingback: Szumma #008 – 2015 38. hét | d/fuel

  8. Daniel says:

    How about some improvements in the way extensions are managed/updated?
    Meaning that all official extensions should be automatically recompiled (if that’s how it works) and available for upgrade.
    Or send some notifications to their maintainers?
    Otherwise what’s the point of upgrading if I can’t work anymore with R#?

    • Matt Ellis says:

      Hi Daniel. We’ll be updating extensions, both first party and third party, as the EAP continues, when the SDK becomes available. We already work with the community of extension developers to notify them of updates to the SDK and to help with updating their projects to work with new versions, either as advice, or as pull requests.

      Do you have any particular extensions in mind?

  9. Bernard says:

    Roadmap for .tsx files?

    Alternatively, is there a way today to make the .tsx files appear as if there are .jsx from Resharper standpoint?

    • Anton Lobov says:

      Support for .tsx files will appear in the next EAP of ReSharper 10 (done and merged already).

      >is there a way today to make .tsx appear as if they are .jsx
      Unfortunately, no. Please wait for the next EAP of ReSharper 10.

  10. Dominique says:

    Latest 9.x release…sucks
    Resharper 10 EAP1 … sucks
    Resharper 10 EAP2 … sucks
    Resharper 10 EAP3 … sucks

    I have to program c# / js (ES6) w/o resharper for quite a while now since resharper is crashing / freezing my Visual Studio 2015 every N minutes.

    I can give you a live demo if this helps. It’s reproducible.

    If Resharper 10 (final) will not fix this issues then i will finally dump resharper.

    • Jura Gorohovsky says:

      Dominique, sorry for replying late: your comment has somehow got in my spam folder.

      We’d love to fix for sure. I’m not sure if a live demo helps but we’d appreciate a sample solution or any hints that could help us reproduce the problem on our hardware.

      Can I ask you to drop a line to ReSharper support? I told them about your issue, they’re looking forward to work with you to reproduce and fix it.


Leave a Reply

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