Meet ReSharper 7.1.2, dotTrace 5.3.1 Performance

Two quick maintenance releases to our .NET tools become available today: please download ReSharper 7.1.2 and dotTrace 5.3.1 Performance.

ReSharper 7.1.2 contains fixes to Find Usages (RSRP-336714) and auto-completion in XAML (RSRP-337050), brings a pack of unit testing improvements related to running MSTest fixtures in Visual Studio 2012 (here’s the list of fixes), and adds more updates to the installer.

dotTrace 5.3.1 Performance fixes fetching PDB files required for code preview (DTRC-8228), and improves installation in certain scenarios.

If you’re experiencing any of the issues mentioned above, please try out these new updates. However, if previous releases are working fine for you, it’s probably best to just stick with them.

Comments below can no longer be edited.

9 Responses to Meet ReSharper 7.1.2, dotTrace 5.3.1 Performance

  1. Avatar

    Daniel says:

    February 20, 2013

    ReSharper has an “Updates” option, with this text: “Download the list of available updates from the Web”.

    I have ReSharper 7.1.1 in VS 2010 but it doesn’t show any updates.

    One more thing, after upgrading from 7.1, I have now 2 ReSharper installations: v7.1 and v7.1.Vokiqiq.
    And all this for only 80 EUR (upgrade)…

  2. Avatar

    Jura Gorohovsky says:

    February 20, 2013

    We’re not giving a notification on 7.1.2 because it contains very targeted fixes, meaning that most 7.1.x users wouldn’t tell any difference, so why bother them?
    Reg. two installations, how many Visual Studio versions do you have installed on your machine? Is it possible that you have 7.1 installed in one VS version and 7.1.1 in another VS version?

  3. Avatar

    Daniel says:

    February 20, 2013

    I have only VS 2010 installed.

  4. Avatar

    kfalk says:

    February 20, 2013

    @Daniel The latest R# 7.1.2 has critical fixes related to installer. So, if you have not only one R# instance under installed programs do not panic. Just try to uninstall both of them and reinstall R# 7.1.2 again.

  5. Avatar

    Daniel D says:

    February 21, 2013

    Still have problem with mstest runner. Stopping the tests (2 time press on stop button) does not stop the vstest.executionengine_x86.exe and all tests continue to run. They are also being updated (goes green) in the test list.

  6. Avatar

    kfalk says:

    February 21, 2013

    Daniel, could you please mail me directly via Also, please provide more detailed information about VS version / edition, type of projects. Is it reproducible on a simple MsTest project. Thnx

  7. Avatar

    David says:

    February 26, 2013

    Let me repost my feedback for the previous release of ReSharper – it is still broken exactly the same way. All my MSTest unit tests are failing because the CONFIG file that they depond on are not present in the folder where ReSharper runs the tests.

    === Original message from ===
    My issue is that I have a project that has two CONFIG files. One is App.config that is correctly copied into the Out folder during unit test run. Another config file (this is a config for one of the dependent DLLs and it contains the DLL configuration). This second DLL is configured in the project to be copied into the output:

    <None Include="MyConfig.config">

    This second DLL is copied correctly to the bin/Debug folder during build but it is not present in TestResults{unique folder name}Out folder and because of that the unit tests fail.

    Le me know if you need more info to reproduce the issue.


  8. Avatar

    Someone says:

    March 1, 2013

    “We’re not giving a notification on 7.1.2 because it contains very targeted fixes, meaning that most 7.1.x users wouldn’t tell any difference, so why bother them?”

    I think you are overlooking one important fix: 7.1.1 did not work well with .sqlproj files. 7.1.2 appears to fix that.

  9. Avatar

    Jura Gorohovsky says:

    March 1, 2013

    @Someone That’s an unexpected change, to be honest. Changes related to .sqlproj handling are being made for 8.0, not for 7.1.2. However, great to know it’s now working well for you )

Discover more