ReSharper 2016.3

In this post, we're going to look at how ReSharper 2016.3 can help you unit test your .NET Core applications and libraries. Sadly, before we can look at this, we have to deal with the confusing issue of what versions of .NET Core are supported. TL;DR: ReSharper 2016.3 works with .NET Core projects in Visual Studio 2015 and Visual Studio 2017 "RC", but unit testing only works in project.json based projects. The IDE interface to dotnet test was rewritten for the .csproj based projects in Visual Studio 2017 "RC" and only just documented. More details at the end of this post. Unit testing i

When we released ReSharper 2016.3 (and earlier this week, ReSharper 2017.1 EAP), we introduced initial support for C# 7 and VB.NET 15. For example, ReSharper now understands binary literals and digit separators, as well as local functions with several inspections. We're far from feature complete, but want to look ahead at what's coming in terms of new programming language features and what we are working on for ReSharper (including some of the challenges building out those features). Here goes! In this post: Digit separators and binary literals Local functions Output variables C#

If you are a long-term user of dotTrace Timeline Viewer, you've likely noticed some UI changes in dotTrace 2016.3. What has changed exactly and, more importantly, why were these changes made? Read on to find out. (more…)

ReSharper offers hundreds of quick-fixes and context actions. As you remember, quick-fixes are aimed to resolve a certain problem in your code, whereas context actions allow you to quickly introduce some minor changes. Today we are going to review several quick-fixes and context actions that simplify your work with method parameters in C#. Some of them have been available for years, some have only been added in the most recent release. (more…)

ReSharper's code generation actions can create a lot of code for us. Why manually write a constructor that initializes type members? Why manually implement interface methods and properties? ReSharper can do those things for us! Some say developers who use tools to generate code are lazy. Personally, I like to call that efficient. Instead of writing code that is, in essence, programming language ceremony, we can let ReSharper generate it for us and focus on implementing business value and solving our customer's problem instead. In this post, we'll go over some of the newly introduced and upd

We are starting the new year with a bugfix update for ReSharper Ultimate 2016.3. All in all, it addresses 50+ issues in ReSharper, dotCover, dotTrace and ReSharper C++. ReSharper 2016.3.2 includes minor fixes in code analysis and highlighting, automatic code completion in TypeScript, and generation of Dispose pattern implementations. It speeds up the Inline Parameter refactoring and corrects parameter positions in the Change Signature refactoring. Find Usages receives an action to stop the current search. We've also fixed unfortunate bugs from the previous bugfix related to ReSharper Build

If you use dotTrace, you probably know it consists of two independent applications for performance analysis: Performance Viewer and Timeline Viewer. One of the greatest features that made Performance Viewer so helpful for quick performance evaluation was Subsystems. In dotTrace 2016.3, Subsystems have finally made it into dotTrace Timeline Viewer. What are subsystems? The mechanics of Subsystems are quite simple. In most cases, each subsystem just groups calls made within a certain namespace or assembly: WPF, LINQ, collections, strings, and so on. There are also certain special subsystems

Today we'd like to recap the most important changes in navigation and search that were introduced in ReSharper 2016.3. Find Results window is populated asynchronously If your solution is large enough, finding references of heavily used symbols can take time, delaying work with your code. To address this issue, we updated the usage search mechanism to make it async. Both Usages of Symbol pop-up and Find Results window are filled asynchronously, allowing you to work with partial search results. If you invoke Usages of Symbol (Shift + Alt + F12) and notice that search is taking a long time,

dotTrace 2016.3 introduces a new Events window which is available in both standalone dotTrace and dotTrace integrated in Visual Studio. To open the window in the standalone Timeline Viewer, use the View | Events menu: In Visual Studio, click Show Events in the Performance Profiler window: (more…)

After we released the initial continuous testing support in dotCover, the most popular response was "Cool, but this could be a lot more useful if highlighting was able to indicate test results." Indeed, before 2016.3, dotCover's highlighting was used only to indicate code coverage: dotCover 2016.3 finally addresses the issue. First, we got rid of colored backgrounds. Now, we use a small colored marker in the left gutter. Second and most important, we've completely changed the highlighting logic. Now, it not only shows whether a statement is covered by tests but also indicates test resul

ReSharper Ultimate 2016.3 introduces a new infrastructure for language injections in string literals, which enables ReSharper to treat particular string literal contents as a piece of code written in one of the supported programming languages: C# or ECMAScript regular expressions language, CSS, HTML, JSON or JavaScript. You can inject a language into a string literal in one of the following ways. Method 1: "Mark as injected language" context action When you open the Alt+Enter menu on a string literal, you’ll see a "Mark as injected language" item. In the submenu, choose one of the sup

Looking for a bugfix release? We have one! ReSharper Ultimate 2016.3.1 is now available for download. This update addresses a selection of issues in ReSharper and ReSharper C++. ReSharper 2016.3.1 is mostly about integrating into Visual Studio 2017 RC. We've received a lot of complaints about 2016.3 not detecting a Visual Studio 2017 RC installation. In all cases, repairing the Visual Studio installation would fix the issue, and based on this experience, we've updated the installer to detect (and warn about) incomplete Visual Studio installations. Other than that, the new ReSharper fixes