ReSharper 6.1, dotCover 1.2 and dotTrace 4.5.2 Performance Released

Christmas is only a few days away and we’ve decided to celebrate it a little earlier by releasing not one, but all three of our main .NET tools: ReSharper 6.1, dotCover 1.2 and dotTrace 4.5.2 Performance.

ReSharper 6.1

As covered in previous posts, this release of ReSharper is much more than a few bug fixes.

Settings

In ReSharper 6.0 we laid the foundations for what would be the new settings management engine. This was quite a substantial change, both from an architectural point of view as well as functional. Unfortunately due to that pesky little annoyance called time, we did not manage to finish it for the 6.0 release. We have now though and ReSharper 6.1 introduces a wealth of new possibilities for sharing settings across solutions, teams, machines and even company-wide policies. And we’re still not done with settings, so keep your feedback coming for further releases.

image

Performance improvements

For every single release of ReSharper, we invest a large amount of time in performance improvements. This often isn’t an easy task since new releases also include new functionality. In 6.0 we had some serious performance issues with certain types of web projects. This has now thankfully been resolved in 6.1 and we’ve made 6.1 faster in many areas. Numbers are impressive: we have fixed 140 performance problems for 6.1.

Async and Visual Studio 11 support

Async support in C# is still in CTP stage. Visual Studio 11 is in early developer preview. Trying to support technology that is not entirely finished proves not only challenging but also risky. Any major changes could deem most of the work we’ve performed as obsolete. However, we know that you, our users, play with the early bits and miss ReSharper.

image

That’s why in 6.1 we provide support for Async features in C# and VB.NET, as well as initial experimental support for Visual Studio 11. Support for Metro style applications is not yet included, and in order to install ReSharper into VS11 Developer Preview, you have to use a separate .vsix installer available at ReSharper downloads.

Optimizing assembly references

Many users rely on ReSharper in streamlining their project maintenance tasks, and this new feature is a nice addition to the existing project-level toolset. In any project in your solution, ReSharper 6.1 detects assembly references that are not effectively used, and helps remove some or all of them.

image

SDK

During 6.0 development we invested heavily in trying to provide a better API for extending ReSharper. 6.1 also sees the birth of this effort. Along with an improved API, we also now provide a testing framework, Visual Studio templates for creating plug-ins, samples, as well as online documentation. ReSharper 6.1 SDK is available for download as a .msi or .zip package.

image

More awesome features

Here are a few more great features also added:

  • Structural Search and Replace for HTML and ASP.NET. You can now use Custom Patterns to refactor both HTML and ASP.NET markup.
  • Call tracking for ASP.NET MVC. Same call tracking features, extended to ASP.NET MVC 3.
  • New code inspections. Access to disposed closures, covariant array conversions and more.

We have also fixed many outstanding issues. Look for more blog posts describing 6.1 features and improvements in future here on the JetBrains .NET tools blog.

dotCover 1.2 and dotTrace 4.5.2 Performance

These are mainly maintenance releases with a primary focus of supporting ReSharper 6.1. In addition, dotCover 1.2 works side-by-side with TypeMock 6.2.x, provides performance improvements in report generation, reduces HTML report size and memory consumption.

Note that we are already working on next major dotCover and dotTrace Performance releases. EAPs are expected soon, exposing a ton of new functionality and improvements, so stay tuned for that.

Download them all!

You can download ReSharper 6.1, dotCover 1.2 and dotTrace 4.5.2 Performance right now!

Last but not least, we’d like to wish everyone very Happy Holiday season. Stay safe and see you all in the New Year!

This entry was posted in dotCover Tips&Tricks, dotPeek Tips&Tricks, dotTrace Tips&Tricks, News and Events and tagged , , , , . Bookmark the permalink.

18 Responses to ReSharper 6.1, dotCover 1.2 and dotTrace 4.5.2 Performance Released

  1. Markus Springweiler says:

    ReSharpers yesterdays nightly build rating — 1.5 stars out of 5 — looks very promising, doesn’t it?

  2. Markus, something doesn’t work for you?
    What’s exactly?

  3. Joe White says:

    1. I’m kind of curious what it is about Metro apps that makes them a different beast for ReSharper. Does WinRT require different work to provide Intellisense? Then again, non-Metro apps can use WinRT too, and you didn’t say there’s any problem with them. Or maybe it’s just that they use a different subset of the Framework?

    2. Can ReSharper extensions be packaged as .vsix files, and/or installed per-solution? If so, it would be great if you could eventually provide custom feeds so R# users could see community-submitted extensions in VS’s Extension Manager (after adding your feed to the list) and/or in NuGet.

  4. orangy says:

    Joe,

    1. WinRT project system, at least for Developer Preview, doesn’t provide us with ANY reference information. So we are waiting for something fixed from Microsoft to continue.

    2. OpenWrap has ReSharper-plugin-feeding functionality. It’s not VSIX, it is custom solution. VSIX is per-machine installation vehicle.

  5. Markus Springweiler says:

    /Default/CodeInspection/Highlighting/UsageCheckingInspectionLevel/@EntryValue is still stored in a user specific file (version control agnostic).

    Which old settings files can now safely be deleted after 6.1 has imported everything into the new dotsettings files?

  6. Adrian says:

    Small Bug: ReSharper Async CTP: AsyncCtpLibrary_Silverlight5.dll (Silverlight 5) should also be valid to not show the async C# 5.0 Feature notify

  7. Alexander says:

    I installed 6.1 and there’s no *.DotSettings file for my solution team-shared options. *.6.1.ReSharper file instead. What is wrong?

  8. Vasiliy Aksyonov says:

    *traditional question about new EAP start date*

    Alexander, you have to change something and choose “Save to team-shared” in Options dialog

  9. ckaut says:

    New options dialog has very blurry not readable text. Fix this please…

  10. @ckaut
    We would certainly fix it if it was observable for us.
    In order to investigate the problem, we’ll need a bug report from you with a screenshot showing the appearance of the Options dialog on your machine, and probably your system info.
    Thank you

  11. Eric Wang says:

    Thank you very much for your effort. Your tools is so great.

  12. Luis Abreu says:

    Excellent work guys!

    Quick question: why have you stopped the nightly builds for vs 2011?

  13. @Luis
    We don’t think this is worth the effort at this time as integration points with VS11 are very likely to change between public previews of VS11.
    As soon as a new VS11 preview build comes out, we won’t take too much time before providing a ReSharper build that supports it.

  14. Luis Abreu says:

    Ok @Jura.

    Since I’ve started migrating my apps to .NET 4.5, I’ve been passing more and more time in VS 2011 and I can tell you that I really miss R#!

  15. @Luis
    Is there anything that prevents you from using the VSIX installer for VS11 available on ReSharper downloads?

  16. Sinae says:

    Still I’M VERY TIRED OF RESHARPER BUGS AND ITS SLOW as helll…

    Yet i have to use it for simple things that i just live can’t without…
    I really really wish you would fix those bugs and performance problems…
    and we should be able to disable everypart of resharper we don’t need or want.

  17. Sinae says:

    just disabled code analysis maybe that was the reason editing xaml was so slow

  18. @Sinae
    Which of the following 6550 unresolved bugs and 94 outstanding performance problems are you referring to?

    We’ll be happy to investigate problems that you’re facing but we need to know exactly what they are. Specifically with performance problems, there’s a procedure for taking performance snapshots of VS+ReSharper and submitting them to us for investigation. We consider performance a top priority but in order to improve it, we need to see what’s going on when the code executes, and it’s simply not possible without a performance snapshot.

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 class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">