Overview of dotTrace 6 Timeline Profiling

Different profiling methods and options in dotTrace 6 In our announcement post for dotTrace 6, we introduced a new profiling method: Timeline profiling. Let’s explore what it is, how it can help us and how it compares to other profiling methods like sampling, tracing and line-by-line profiling.

We’ll also have a look at the Timeline Viewer and see how we can analyze a performance snapshot that was captured using this new profiling method.

The Timeline Profiling Method

When using timeline profiling, dotTrace collects temporal data about thread states, application events, memory allocation, garbage collections, I/O operations and other multi-threading data by using Event Tracing for Windows (ETW). Having all this information available and bound to a timeline, this profiling method is ideal for analyzing UI freezes, excessive garbage collections, uneven workload distribution, insufficient I/O and so on.

The Timeline Viewer lets us view all events and zoom in on a particular timespan of our application’s runtime. We can see which calls were made by our application, how these calls were distributed over time, on which tread they ran and when I/O was involved. We can even see the source code for the selected method, giving us all context we need to dive into the data presented.

dotTrace 6 timeline profiling using ETW analyzes threads, memory, I/O

What’s the Difference with Performance Profiling?

From a birds-eye perspective, dotTrace 6 now provides two methods of profiling applications: performance profiling and timeline profiling. In most cases, we can interchange both profiling methods. Since they both collect call stack data, we can use them to determine performance bottlenecks in our .NET applications. There are some important differences though:

  • With performance profiling, dotTrace collects call stack data, data about call timings and data about the number of calls. This lets us analyze how much time is required to execute a particular method and how often it is called, and lets us trace the method call path.
  • With timeline profiling, dotTrace records application events and data about how application and thread state changed during the profiling session. This lets us see what calls were made by our application, but more importantly, it also shows how these calls were distributed in time. This is very helpful when analyzing behavior of multi-threaded applications where the chronological order of events typically matters a lot. For example in determining synchronization delays, UI freezes and so on.

Timeline profiling is less suitable for measuring exact call numbers of every statement. As a rule of thumb, use performance profiling if the analysis leans more to finding the slowest method in an application, and use timeline profiling to identify the cause of UI freezes and the effects of garbage collection, I/O and other multithreading issues like irregular work distribution, lock contention, serialized execution, and other.

More information about the differences between both profiling methods is available in the web help.

Timeline Profiling an Application

After downloading, installing and starting dotTrace 6, we have two options to start profiling an application. If integration with Visual Studio is enabled, we can use the ReSharper | Profile | Profile Startup Project (Performance) menu from there. dotTrace can also be launched standalone, after which we can use the home screen to start a profiling session. Make sure to provide the path to the executable to profile, and select Timeline as the profiling type.

After clicking Run, our application will be launched with the profiler attached. The profiling controller window also opens, which we can use to start and stop collecting snapshot data, kill the application that’s being profiled and more. We can expand the controller window to view real-time memory and CPU usage and the processes involved in the profiling session.

Profiling controller (expanded)

After reproducing an issue in our application, for example by evoking a UI freeze or following the steps someone provided in a bug report, we can collect a timeline profiling snapshot by clicking Get Snapshot’n’Wait in the controller window. This will open the Timeline Viewer in which we will analyze the snapshot we’ve just captured.

Analyzing a Snapshot using the Timeline Viewer

Once a snapshot is opened, either by capturing a fresh one or opening a previously captured snapshot from the dotTrace Home, we will see the Timeline Viewer and its components. Please note that depending on contained data snapshot processing can take a while. Since the main idea behind timeline profiling is collecting temporal call stack and thread state data, the timeline diagram takes a prominent place showing CPU utilization across various threads over time.

Timeline Viewer showing timeline diagram, filters, call tree and source view.

Analyzing a snapshot using the Timeline Viewer is done by applying filters. Pretty much every tool window can be used to set a filter. The most logical filter tool window is, well, the filter tool window. Imagine we’re interested in seeing only File I/O, we can click that and if needed, specify more fine-grained options like a specific file or the access method (read/write).

Filters tool window

Selecting a filter in one tool window applies it in all the other tool windows. In our example here, filtering File I/O on the file 3.txt tells us where in our application’s runtime the file was accessed if we look at the Timeline Diagram. Our I/O seems to have happened at a little more than 1 minute in, on the thread with ID 3488. Again, we can apply more filtering here. We could select just that thread and show only data for it. Or zoom in on the timeline and select just the timespan where this file was accessed. Or both. No matter what, we’re applying additional filters if we do that.

Timeline diagram filtering

In the Call Stack tool window, we can find the call tree for everything that happened in our application during the selected timespan, on a thread with ID 3488, related to File I/O on the file named 3.txt. We can see a method named ProcessFiles spent time reading and writing files. In the Source View tool window, we can even see the source code for that method obtained by looking for PDB files or by decompiling our application’s assembly.

Call Stack Source Code

By combining filters, we can find the information we want and investigate almost every aspect of our application.

Give dotTrace 6 a try, there’s a free trial available! We have a tutorial available that helps getting started with Timeline Profiling in dotTrace 6, and a more advanced one where we analyze an application issue. We’re looking forward to your feedback! Comments, issues and suggestions are welcome in our issue tracker or through the comments below.

Posted in dotTrace Tips&Tricks | Tagged , , , , | Leave a comment

Type Dependency Diagrams in ReSharper 9

In ReSharper 8, we introduced the concept of Architecture Tools as ways of visualizing the state of module dependencies in your solution. In ReSharper 9, we have augmented these tools with an ability to visualize class dependencies too.

Dependencies between types are shown on a Type Dependency Diagram. You can make one by selecting any node from the Solution Explorer (you can pick a file, folder, project or the whole solution) and choosing Show Type Dependency Diagram. You will see something similar to the following:

Type Dependency Diagram in ReSharper 9

In addition, sometimes you need to investigate which external modules you depend on. In this case, you can once again open Solution Explorer, but this time pick a couple of references, right-click and choose Show Usages on Diagram in order to see how your code depends on the selected modules.

Show Usages on Diagram in ReSharper 9

This yields the following diagram:

Dependence of one type on another on a diagram

Just as with the project dependency diagram, arrows are used to indicate the dependence of one type on another, and the width of the line indicates the relative number of usages of one type from another. The diagram is capable of showing usages, aggregation, inheritance relationships, return type usage and even the use of constructor injections.

Both the types and the lines connecting them show additional navigation options if you hover the mouse over them. In the case of the types, you get to see the references and usages, with plenty of navigation hyperlinks:

References on Type Dependency Diagram

Edge-related popups are similar, showing the usages:

Usages on Type Dependency Diagram

It is also possible to collapse the groups in which the particular types are shown. If you do, the popup for the collapsed group will show how all the types inside this group depend on some external module.

It’s important to note that the diagram is very flexible in terms of content. Some of the things it supports are:

  • Component removal: simply select a type and press Delete to get rid of it. The diagram will fluently readjust itself.
  • Types can be added via simple drag-and-drop: grab an element on the Solution Explorer, drag it onto the diagram, and you’re done. Also, as an added bonus, you can select a class name right in the text editor and drop this onto the diagram canvas to add the desired class!
  • Types can also be added if you simply start typing right on the diagram. This will result in a search (similar to Go to Type) and, after you pick a particular element, that element will be added to the diagram.
  • You can also filter out particular types of elements:
    Filter for types on a diagram
  • You can drag an element on the type diagram to a different folder or project. This will automatically invoke the Move refactoring.

Type Dependency Diagram controls

The right side of the diagram also contains the controls for zooming and panning, but also has two large buttons for controlling the layouter that’s used for the diagram, and they both cause the graph to be laid out in a specific way.

The Inheritance Hierarchy Layouter is more suitable for one big inheritance hierarchy, whereas the Business Logic Layouter is better for a set of non-derived but dependent modules. ReSharper generally tries to automatically determine which layout is better, but you are always at liberty to change the setting.

We hope you enjoy this functionality. If you haven’t got yourself a copy of ReSharper 9 already, a 30-day trial awaits.

Get ReSharper

Posted in ReSharper Tips&Tricks | Tagged , , | 1 Comment

Navigation Improvements in ReSharper 9

As is customary, every new version of ReSharper comes with improvements across the board, so in this blog post we are going to focus on Navigation and related features.

Universal Alt+Enter

Let’s face it: Alt+Enter is a primary shortcut in ReSharper and we, on our end, have given this shortcut plenty of power, starting with using it just for context actions and quick-fixes and extending it to support for things like unit testing.

Now we’re taking this one step further by exposing all actions that are provided by ReSharper in a single, unified Alt+Enter menu. So now, if you press the shortcut on a chunk of code that is not an inspection, ReSharper will present you a menu with some of the possible actions you can take at this point:

This popup is also searchable, and the search happens on all of ReSharper’s actions:

Navigate to Exposing APIs

Quite often, when given a particular type (say, IFoo), you want to find out the sum total of all the ways in which you can actually get an instance of this type. There are lots of possible sources: static and ordinary fields, method return values, out parameters, and others. ReSharper’s navigation menu now includes an item called Navigate to Exposing APIs that helps you do exactly that:

Assembly Explorer Navigation

In recent past, dotPeek’s Assembly Explorer has migrated to ReSharper to provide a navigation tree for decompiled items. In ReSharper 9, we have added a few tweaks to make sure it’s more accessible. First of all, we’ve added an appropriate item to the Navigate To menu:

You can also navigate to the Assembly Explorer directly from VS’s own Solution Explorer:

It’s also possible to configure exactly what happens during navigation to a type whose sources are not locally available:

And a few extras…

Just a few more features to cover:

  • The Go to Type mechanism is now disambiguated for generics, meaning that navigating to a declaring type of a variable of type List<Foo> will now take you to either List<T> or Foo:
  • Find Usages now uses the Preview Tab feature in Visual Studio. This is a configurable setting that you can find in ReSharper Options:
  • The Find Usages mechanism no longer blocks the UI thread for long-running searches, so you can keep working with code while a search is in progress. That said, we did quite a lot to reduce search times in this release, so we kind of hope you don’t notice this feature at all.
  • We also made a couple of improvements to the Find Results window. ReSharper will not reuse tabs so that multiple searches for IFoo will show up in a single tab. Also, it is possible to ignore or hide search results. You can press Delete with a search item selected, and it will be grayed out. You can then show/hide the ignored items using the toolbar.

Try ReSharper

Posted in ReSharper Tips&Tricks | Tagged , , | 1 Comment

Bulk Fixes and Refactorings in ReSharper 9

One of the key aspects of ReSharper’s operations is the ability to perform changes in bulk — for example, a bulk option to remove unused using directives can affect hundreds of files, while preserving the overall integrity of the solution. In ReSharper 9, we have improved upon this functionality with even more support for global changes that can be made instantaneously.

Bulk Import

When you import a chunk of code, ReSharper is now able to look through the code in your solution and generate the appropriate imports for all the types:


It is, of course, possible to choose between importing a single chosen type rather than all possible types:

It’s worth noting that, in addition to ordinary member methods, extension methods get imported as well. The only case when R# is unable to import a type is when it resolves to two different namespaces (e.g., System.String and User.String).

Removing Redundant Code

ReSharper has already had fixes for removing redundant unused directives globally, but now we’ve expanded this idea to remove all redundant code across the solution. Furthermore, there are two options here. First, you can apply any one particular inspection across a variety of scopes:


Alternatively, you can remove all redundant code in one fell swoop:


Global Naming Fixes

If you import someone else’s code, it’s likely they are not using the same naming convention that you are. Previously, you would have had to go through each of the elements and apply a fix for every one of them. In ReSharper 9, you can apply the changes en masse:

Invoking a fix brings up a dialog showing what will be renamed and where:

Move to Namespace/File

We’ve made an improvement to the Move to Namespace and Move to File actions, ensuring that, if a single file has multiple class declarations, all of those declarations get moved:

Death to Regions

Not all of us like regions. Some of us positively do not. So when you import someone else’s code and that someone is particularly zealous about using regions, you can now undo that travesty globally with one command:


This blog post has outlined a number of the most visible types of bulk fixes in ReSharper – there are certainly a lot more, including those related to JavaScript and TypeScript. We hope you enjoy these bulk fixes in ReSharper 9!

Get ReSharper

Posted in ReSharper Tips&Tricks | Tagged , , , | 2 Comments

Working with dotTrace Home

When we announced the dotTrace 6, we’ve already had a quick look at the new starting point in our performance profiler: the dotTrace Home. We can use it to start a new local or remote profiling session for known .NET application types, attach to a running process, configure our profiling session and more. Let’s have a closer look!

dotTrace Home

Starting a Local Profiling Session

Left-to-right, dotTrace Home shows us three panes. The leftmost pane lets us pick the action we want to perform, such as starting a profiling session. Next, we can select the application type or process we want to profile from the middle pane. On the right, we can specify additional options for the profiler, such as the profiling type or application startup arguments.

Let’s start a new local session. We can profile an application that we want to be launched by dotTrace, or attach the profiler to an already running process. dotTrace 6 lets us profile a variety of application types:
Application types that can be profiled using dotTrace

  • Standalone application, such as a Windows desktop or console application;
  • Windows Store applications;
  • Silverlight applications;
  • ASP.NET and ASP.NET-like webservers, for example with OWIN based webservers such as Kestrel, self-hosted Web API’s, Nancy and so forth;
  • WCF Services;
  • IIS or IIS Express-hosted web applications;
  • Windows Services;
  • Any other .NET process.

Under the Profile Running Process section, we can choose to attach to an already running process. All processes that are running under .NET 4 or higher that are visible to the current user will be shown and can be attached to. Running dotTrace 6 with administrator privileges will show additional processes that are available to administrators only.

Starting a Remote Profiling Session

For those performance problems that only happen in staging and production which somehow can never be reproduced on our local machine, dotTrace 6 lets us profile remote applications, too. All we have to do is make sure that the dotTrace Remote Agent is copied onto the remote server and then connect to it from dotTrace.

Next, we can enter the URL to our remote agent, typically something similar to http://hostname:9000/RemoteAgent/AgentService.asmx. dotTrace will then show us a list of running processes on the remote server which we can connect the profiler to.

Profiler Options and Profiling Types

Once we select an application type or a running local or remote process, we can tell dotTrace our profiling preferences. These will differ based on the application type we want to profile, but in general we can specify some specific details for launching or connecting to the application and pick the profiling type.

dotTrace 6 provides us with four profiling types that collect performance data in different ways:

Profiling types including new timeline profiling

  • Sampling provides accurate time measurement of calls, but can not reliably measure the number of calls. Sampling is recommended for most cases and is ideal when looking for performance issues in our app for the first time.
  • Tracing provides accurate calls number measurement, but time measurement may be inaccurate due to profiler overhead. It’s an ideal way of profiling and analyzing algorithm complexity, when info about the exact number of calls is more valuable than exact call time values.
  • Line-by-line measures call numbers of every statement in our code and lets us see how many times a line of code was executed. Call time values are inaccurate due to huge profiler overhead.
  • dotTrace 6 introduces a new Timeline profiling type, which collects temporal data about thread states, application events and other multi-threading data using Event Tracing for Windows (ETW). It’s less suitable for measuring exact call numbers of every statement, but it comes in very handy when analyzing multithreaded applications. It not only allows us to see which calls were made by our application, but also how these calls were distributed over time.

Ticking the Advanced checkbox reveals some additional options, for example letting us use the profiler API from our code.


In the left pane of dotTrace Home, recent profiling sessions and snapshots will be shown. After selecting a previous session, we can run a new session with the same settings. Ticking Show details expands any previous snapshot that was captured and shows memory and CPU usage over time. We can then re-open these snapshots and continue analysis of our application.

Recent snapshots and profiling sessions

Recent snapshots and launches can be annotated with comments or a description of what we were investigating. dotTrace also lets us export snapshots to a file so we can distribute them amongst team members. Or have a client capture a snapshot and send it to us for further analysis.

Annotate and export snapshots


Performance profiling is a complex topic. Applications typically execute a lot of statements, may start multiple threads, generating a lot of data. From dotTrace Home, we can call up a series of tutorials that explain how the different aspects of .NET performance profiling work and how we can use dotTrace to analyze our application’s behaviour.


Give dotTrace 6 a try! All feedback, comments, issues and suggestions are welcome in our issue tracker or through the comments below.

Posted in dotTrace Tips&Tricks | Tagged , , , | Leave a comment

Bug Fix Update to JetBrains .NET Tools is Available

Having released ReSharper 9.0 RTM just recently, we’re following up with a minor bug fix update today. Please download and install ReSharper 9.0.1 for 100+ hot and important fixes in the following areas:

  • Unit test runner: 9.0.1 fixes freezes, crashes, performance problems, inability to find any unit tests in certain scenarios, and more.
  • Code analysis: fixes in this area cover JetBrains ReSharper annotations NuGet package, false positive ambiguous invocation, etc.
  • Installation: memory consumption is reduced, and the installer now notifies you about products to be uninstalled in case of incompatibility.
  • Feedback center: a set of fixes for the built-in self-profiling tool.

For the entire list of fixes, please see ReSharper 9.0.1 release notes.

Along with ReSharper 9.0.1 we are rolling out a new EAP build of ReSharper C++. Apart from bug fixes and performance optimizations it introduces a new context action to remove unused #include directives in the scope of a file. We’ve also added a set of new quick-fixes to convert a type alias to typedef or remove unused parameter name. In addition, Remove redundant qualifier learns to operate in the scope of a file, a project or the whole solution.

Other JetBrains .NET tools get minor updates as well. Specifically, dotTrace receives important fixes in terms of profiling unit tests for Windows Store apps. dotCover 3.0.1 refines remote coverage and handles removing temporary snapshots better. Please check dotCover 3.0.1 release notes for the full list of fixes.

Posted in dotCover Tips&Tricks, News and Events, ReSharper Tips&Tricks | Tagged , , , | 12 Comments

Watch ReSharper C++ Session from JetBrains Night in London

The video recording from our JetBrains Night in London that took place on December 2nd, 2014, is now available.

In this video Dmitri Nesteruk shows off ReSharper C++ which is currently available through the Early Access Program. Watch this video to learn more on how ReSharper C++ can help you by providing live and surround templates and by letting you quickly create a constructor or add missing members with code generation functionality. ReSharper C++ is also ready to find and fix code issues on-the-fly and easily perform refactorings.

0:00 – Introduction
8:21 – JetBrains tools for C++ development
9:17 – File templates in ReSharper C++
10:50 – Code generation
14:48 – Macro calls substitution
22:43 – Rename refactoring

Posted in How-To's, ReSharper Tips&Tricks | Tagged , | 3 Comments

Webinar Recording and Q&A: What’s New in dotTrace 6

The recording of our December, 16th webinar with Maarten Balliauw, What’s New in dotTrace 6, is now available on JetBrains YouTube Channel.

In this webinar Maarten explores the new dotTrace 6 release that delivers a great deal of new and exciting profiling goodies: New profiling method — Timeline, restyled staring point for profiling sessions — dotTrace Home, enhanced controller with realtime profiling data, refined Performance viewer, more flexibility for Subsystems, shared platform for all JetBrains .NET tools, and more.

0:00 Introduction
0:10 Unified instaler and shared platform
1:52 dotTrace Home
3:05 Remote profiling
4:50 Recent snapshots
6:20 Recent launches
7:19 Tutorials section
8:20 Profiling types
12:14 New profiling controller
15:12 Timeline viewer – overview
18:49 Timeline viewer – investigating an issue
26:04 Performance profiling using sampling
27:20 Performance viewer – overview
30:58 Performance viewer – subsystems
33:20 Visual Studio integration
37:42 Questions

We received plenty of questions during the webinar and we’d like to use this opportunity to highlight some of them here, as well as address the questions that we didn’t have a chance to answer during the webinar. Please find the questions below with answers.

Q: What is the main difference between Timeline profiling mode and other Performance profiling methods?
A: The main benefit of the Timeline profiling is that it allows you to see not only what calls were made by your application but also how these calls were distributed in time. This can be extremely helpful when analyzing behavior of multi-threaded applications where the chronological order of events does matter: for example, in determining sync delays, the cause of UI freezes, and so on. Another benefit is that Timeline profiling collects a wider range of data. In addition to call stack data, it records memory allocation, garbage collection, and I/O events.

Q: Is there any integration with dotMemory for extra information about memory usage?
A: There is no integration currently. They are two different profilers and each has a unique way of visualizing application data. Sampling, Tracing and Line-by-line profiling will capture what is happening in application code and not really look at memory usage there. In Timeline profiling mode we do get some insights on memory usage. Timeline uses on Event Tracing for Windows as a source of information. It makes possible to show events like blocking garbage collection. But if you want to profile .NET memory it’s better to use dotMemory which provide you with much more information on memory usage inside your application.

Q: Does my dotTrace 5 license allows using dotTrace 6?
A: dotTrace 5 has version-based license model: The purchased license is valid for v.5.x. However, dotTrace 5 licenses purchased after November, 1st, 2014 are eligible for free upgrade to dotTrace 6: These licenses are subscription-based and include 1-year upgrade subscription. With any additional questions, you can contact JetBrains sales team and discuss your subscription expiration date or upgrade options.

Q: What ReSharper versions does dotTrace 6 compatible with?
A: dotTrace 6 is compatible with latest ReSharper 9. Please note dotTrace 6 is not compatible with ReSharper 8.x, dotCover 2.x, dotMemory 4.1 or previous versions integrated in Visual Studio. Installing dotTrace 6 will remove these old versions of JetBrains .NET tools from Visual Studio.

Posted in dotTrace Tips&Tricks, How-To's | Tagged , , , | 1 Comment

Improved TypeScript Support in ReSharper 9

In ReSharper 9.0 we tried to help you work with TypeScript as comfortably as you do with other supported languages. Here is a list of features we’ve implemented that were missing before.

Highlightings and Quick-Fixes

Version 9.0 aims to support most TypeScript compiler errors. About 270 different types of error are now highlighted, and quick-fixes are available for many of them. Resolve errors, type compatibility errors, overload resolution errors and accessibility errors are all supported now, too. As you would expect, some common quick-fixes such as Create from usage and Change all now are also available in TypeScript files:

Error Highlighting for TypeScript in ReSharper 9

Of course, the import popup is now here, too:

Import popup for TypeScript in ReSharper 9

New Inspections and Context Actions

Take advantage of new code inspections for TypeScript that cover code redundancies, common mistakes, and suggest better language use:

Error Highlighting for TypeScript in ReSharper 9

Several new context actions are available as well:

New context actions for TypeScript in ReSharper 9


ReSharper 9.0 adds support for the following refactorings, previously unavailable for TypeScript.

Introduce Field

As with the other supported languages, the ‘Introduce field’ refactoring allows you to introduce a field from an element under the caret, or from a selection:
Introduce field refactoring for TypeScript

Copy Type

Copy type creates a copy of selected type and places it into a module you specify:
Copy Type refactoring for TypeScript

Move Refactorings

Four Move refactorings have been implemented: move type to module, move type to file, move into matching files, and move to folder:

Move to Module refactoring for TypeScript

Rename File

This is a brand new TypeScript-specific refactoring. When you rename a file, it helps you update file-based module dependencies, reference comments, and generated JS file references.

Suppose you are renaming your app.ts file to hello.ts:

Rename a file refactoring for TypeScript

All the corresponding references will be updated accordingly:
Rename file refactoring for TypeScript results

Import on Cut-and-Paste

Remember this tiny useful pop-up that appears when you paste code from elsewhere? Now it’s also available for TypeScript:
Import on Cut-and-Paste refactoring for TypeScript

Code Generation

ReSharper 9.0 introduces Generate functionality for TypeScript. Now you can implement interfaces by easily generating missing members, as well as generate overriding members and constructors:

Generate missing members functionality for TypeScript

Other Improvements

Every new version of ReSharper includes improvements to existing functionality, and TypeScript support in ReSharper 9.0 is no exception.

Live Templates functionality has been improved to include new scopes ‘module member’ and ‘type member.’ It also comes with live templates for common TypeScript entities such as classes, enums, interfaces and modules:

Live templates for TypeScript

Parameter info now supports not only function arguments, but generic arguments as well:


Specialized signatures are now supported:
Specialized signatures for TypeScript support

Finally, ReSharper now fully supports contextual typing and TypeScript 1.3 language features such as tuples and the protected keyword:

TypeScript 1.3 support in ReSharper 9

We’ve also added a dedicated Options screen where you may specify your current TypeScript language version to make ReSharper features adapt to that specific version:

Options for TypeScript in ReSharper 9

And last but not least, the set of TypeScript features also inherits new JavaScript features added in v9.0. Stay tuned for more details in upcoming blog posts!

Posted in ReSharper Tips&Tricks | Tagged , | 6 Comments

Webinar Recording and Q&A: What’s New in ReSharper 9

The recording of our recent webinar with Matt Ellis, What’s New in ReSharper 9, is now available on JetBrains YouTube Channel.

We apologize for the technical issues we had with Go To Webinar platform that prevented us from making the second session. If you registered for that session and was not able to attend it, please feel free to watch the recording and ask your questions in comments.

In this webinar, Matt Ellis covers some of the new and exciting features coming with ReSharper 9. These include but are not limited to regular expression support, Visual Studio 2015 Preview and C# 6.0 support, navigation improvements (Go to Action and Navigate to exposing APIs), bulk naming fixes and other improvements to the Fix in Scope mechanic, code style settings and a shared platform for all JetBrains .NET tools.

0:00 – Introduction
2:40 – Navigation
7:10 – Go To Action, Search in Options
10:50 – Code Formatting
13:05 – Code Style
16:01 – Inspections
23:10 – File Layout Editor
27:56 – Type Dependency Diagram
32:44 – Xamarin Forms
33:10 – Shared Project improvements
35:17 – Visual Studio 2015
37:16 – C# 6
41:58 – TypeScript
42:56 – Regular Expressions
46:05 – Code Completion Filters

The slides to accompany this session are available on SlideShare.

We received plenty of questions during the webinar and we’d like to use this opportunity to highlight some of them here, as well as address the questions that we didn’t have a chance to answer during the webinar. Please find the questions below with answers.

Q: Does my ReSharper 8 license allows using ReSharper 9?
A: This really depends on a specific license. If you have a personal license to ReSharper 8 and your upgrade subscription didn’t expire before December 5, it means you can upgrade to ReSharper 9 for free. Commercial licenses to ReSharper 8 may or may not be eligible for free upgrade to ReSharper 9: if in doubt, check your license certificates or contact JetBrains sales.

Q: Will ReSharper 9 keep supporting Visual Studio 2005?
A: No, ReSharper 9 doesn’t support Visual Studio 2005 and 2008, and this is also true for the recently released updates to other JetBrains .NET tools. If you would like to use ReSharper in Visual Studio 2005 or 2008, please use ReSharper 8 that can be downloaded from here. For more information on the state of Visual Studio support in latest JetBrains .NET tools, please see our recent blog post, ReSharper and Visual Studio: Where do We Stand. As to ReSharper 9, it does support Visual Studio 2010, 2012, 2013 and 2015, which includes Visual Studio Community 2013.

Q: Does the upgrade to ReSharper 9 Ultimate stack on top of my current subscription end date? Will it add 12 months on top of my current subscription, or will it reset my subscription to the date of upgrade? Should I just wait until near the end of my current subscription before upgrading?
A: ReSharper Ultimate will reset your upgrade subscription to the date of upgrade. For example, if your current upgrade subscription to ReSharper expires in May 2015, then upgrading to ReSharper Ultimate in December 2014 will result in setting a new upgrade subscription span that will expire in December 2015. That said, if your current upgrade subscription is expiring soon, now is a good time to upgrade to ReSharper Ultimate. However if your current subscription is not yet close to expiring, then unless you need the additional tools included in ReSharper Ultimate as soon as possible, it could be worth waiting before upgrading. With any additional questions, you reach out to the sales team and discuss your upgrade/renewal strategy.

Q: Is ReSharper 9 the same as ReSharper 8 Full Edition? What does ReSharper 9 Ultimate add on top of the regular ReSharper 9?
A: Yes, what we currently call ReSharper is basically what ReSharper Full Edition used to be. ReSharper Ultimate is a single license for ReSharper, ReSharper C++ (not released yet), dotTrace, dotCover, and dotMemory. ReSharper Ultimate also includes a year of free upgrades that is synchronized across all tools that it includes. For more information, please see a recent blog post, Meet ReSharper, ReSharper C++ and ReSharper Ultimate, or visit the ReSharper Ultimate web site that summarizes and visualizes the benefits of the Ultimate offering.

Q: How do you invoke the “Configure Format” action in JavaScript?
A: You can do this by selecting a piece of code and pressing Alt+Enter to invoke the Format Selection menu.

Posted in ReSharper Tips&Tricks | Tagged , | 1 Comment