ReSharper Ultimate 2017.2 EAP kicks off

ReSharper Ultimate 2017.2 Early Access Program is now underway: you are welcome to download and install the latest builds of ReSharper, ReSharper C++, dotCover, dotTrace, dotMemory, dotPeek, as well as various command-line packages that we provide.

So far, version 2017.2 mostly incorporates changes to ReSharper and ReSharper C++. For example, the new ReSharper starts to support C# 7.1, TypeScript 2.3 and Angular 4, has its code completion optimized, offers various navigation improvements, and adds more language injections. ReSharper C++ 2017.2 introduces support for extended friend declarations from C++11, selection statements with initializer from C++17, and more language features.

Please download ReSharper Ultimate 2017.2 EAP, read a quick summary of changes, and expect us to elaborate on the improvements in coming weeks.

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

5 Responses to ReSharper Ultimate 2017.2 EAP kicks off

  1. Pingback: Der Weg zu ReSharper Ultimate 2017.2 -

  2. Pingback: Dew Drop - June 2, 2017 (#2492) - Morning Dew

  3. Theo says:

    ReSharper – Runtime Error – Technical Data
    JetBrains ReSharper has encountered a runtime error.
    Technical data follows.
    Hint: Ctrl+C copies the text of system message boxes to Clipboard.

    Solution was not garbage collected within 30 seconds.

    — EXCEPTION #1/2 [SolutionLeakException]

    Message = “Solution was not garbage collected within 30 seconds.”

    ExceptionPath = Root.InnerException

    ClassName = JetBrains.ProjectModel.SolutionWatchdog.SolutionLeakException

    HResult = COR_E_EXCEPTION=80131500

    — Outer —

    — EXCEPTION #2/2 [LoggerException]

    Message = “Solution was not garbage collected within 30 seconds.”

    ExceptionPath = Root

    ClassName = JetBrains.Util.LoggerException

    Data.ManagedThreadName =

    InnerException = “Exception #1 at Root.InnerException”

    HResult = COR_E_APPLICATION=80131600

    StackTraceString = “

    at JetBrains.ProjectModel.SolutionWatchdog.SolutionWatchdog.SolutionCatcher.c__DisplayClass5.b__4(Int32 count)

    at JetBrains.Util.Memory.LeakWatchdog.c__DisplayClass14.b__13(IMemoryGrave g)

    at JetBrains.Util.Memory.LeakWatchdog.Grave.b__1a()

    at JetBrains.Util.Logging.Logger.Catch(Action action)

    at JetBrains.Util.Memory.LeakWatchdog.Grave.StopWaiting()

    at JetBrains.Util.Memory.LeakWatchdog.SweepWaitingGraves()

    at JetBrains.Util.Memory.LeakWatchdog.OurTimerCallback(Object cookie)

    at System.Threading.TimerQueueTimer.CallCallbackInContext(Object state)

    at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

    at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

    at System.Threading.TimerQueueTimer.CallCallback()

    at System.Threading.TimerQueueTimer.Fire()

    at System.Threading.TimerQueue.FireNextTimers()

    at System.Threading.TimerQueue.AppDomainTimerCallback()


  4. Theo says:

    When editing Typescript projects this error is what I regularly get after shutting down R#. I shut down Resharper if VS becomes unresponsive (which tends to be because of an R# out of memory exception).

    Unfortunately in this state I cannot report the error via the normal interface it seems, hence I posted it here.

    Restarted R# again and it brought down VS2017 altogether… auto-restart VS

Leave a Reply

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