ReSharper 9.1.3 to the Rescue

Visual Studio 2015 RTM users, please be informed that ReSharper 9.1.3 is now available for download, along with corresponding updates to all other ReSharper Ultimate tools.

This update fixes the annoying editor issues that were on display in ReSharper 9.1.2 and that included inverted keyboard input, disappearing caret, and focus switching off the text editor, potentially resulting in Visual Studio crashes.

Additionally, this update fixes ReSharper’s XAML code generation features in Visual Studio 2015 RTM.

If you use Visual Studio 2015 RTM, this is a recommended update for you. If you’re on older versions of Visual Studio, namely 2013, 2012 and 2010, you can skip this update.

If you have previously applied one of the suggested workarounds to improve the behavior of ReSharper 9.1.2, we suggest that you now revert the changes so that Visual Studio uses a single UI for displaying both ReSharper’s quick-fixes and Visual Studio’s quick actions.

We would like to once again apologize for the problems caused, or, to put it the 9.1.2 way, for the psmelbor cdesua.

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

13 Responses to ReSharper 9.1.3 to the Rescue

  1. Kevin Rich says:

    eW areppctiae teh up!dtae


  2. Pingback: ReSharper 9.1.3 to the Rescue  | OPC Diary

  3. TypeScript issues with wrong error message on class not implementing an interface is still there. I posted a thread in the forum but it is still “awaiting moderation”.

    • Anton Lobov says:

      Hi, Alexey. Could you please provide a link to a YouTrack issue for this problem, or create a new issue for that in YouTrack? We’ll investigate the problem. Thanks.

    • Jura Gorohovsky says:

      Alexey, I’ve just moderated your forum message. We didn’t know about this problem until today, and I guess it won’t be fixed until 9.2.x. Please keep in touch with Anton who commented below as he’s actually one of the developers behind TypeScript support.

  4. Pingback: The Morning Brew - Chris Alcock » The Morning Brew #1911

  5. Pingback: Dew Drop – July 27, 2015 (#2061) | Morning Dew

  6. Vaclav Mikeska says:

    Unfortunately the UnitTests runner still doesn’t work. When I am working on new application DNX451, I am not able to execute NUnit test from .dll. It says “Inconclusive” or “Test not run”. I can see the test involved in the execution list, but it doesn’t work.

    Would be nice if it can work like it worked for last couple of years :)

    When I created standard VS test project, it worked as usual. But it’s standard assembly and it cannot reference the vNext assemblies.

    • Jura Gorohovsky says:

      Vaclav, I don’t think that DNX 4.5.1 is supported as a test run environment at this point.

    • Karl Huber says:

      I got that “Inconclusive …” message too, when I tried to run a UnitTest from R#. It turned out that this happens if your TestFixture is distributed over several partial classes. When it assembled all the tests in a single file I was able to execute Unit Tests from R#.

  7. Vaclav Mikeska says:

    One more additional information: This message can be seen:

    [Window Title]
    Unit Test Runner

    [Main Instruction]
    Unit Test Runner failed to run tests

    System.IO.FileNotFoundException: Could not load file or assembly ‘UnTests.dll’ or one of its dependencies. The system cannot find the file specified.


    [Header=OK, Content=]

    [Expanded Information]
    at System.Reflection.AssemblyName.nGetFileInformation(String s)
    at System.Reflection.AssemblyName.GetAssemblyName(String assemblyFile)
    at NUnit.Core.Builders.TestAssemblyBuilder.Load(String path)
    at NUnit.Core.Builders.TestAssemblyBuilder.Build(String assemblyName, Boolean autoSuites)
    at NUnit.Core.Builders.TestAssemblyBuilder.Build(String assemblyName, String testName, Boolean autoSuites)
    at NUnit.Core.TestSuiteBuilder.Build(TestPackage package)
    at NUnit.Core.SimpleTestRunner.Load(TestPackage package)
    at NUnit.Core.ProxyTestRunner.Load(TestPackage package)
    at NUnit.Core.RemoteTestRunner.Load(TestPackage package)
    at JetBrains.ReSharper.UnitTestRunner.nUnit.BuiltInNUnitRunner.RunTests(IRemoteTaskServer server, Dictionary2 tests, Dictionary2 fixtures, List1 explicitly, Boolean useAddins, List1 assemblies)

  8. Sergey Kuks says:

    Vaclav, are you able to create a sample solution for us, please. Last time I tried to use NUnit in DNX project Visual Studio started to build the project forever and never stopped.

  9. Pingback: ReSharper 9.1.3 to the rescue | Software Engineer InformationSoftware Engineer Information

Leave a Reply

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