JetBrains .NET Tools Blog

Do you have ReSharper 5.1.2 installed?

Are you using native Visual Studio IntelliSense?

Are you annoyed by ReSharper turning off Parameter Information and auto-completion when you open new files?

If your answer is “yes, yes and oh yes”, please download ReSharper 5.1.3.

ReSharper 5.1.3 provides exactly one bug fix that prevents disabling Parameter Information and auto-completion when you’re using native Visual Studio IntelliSense (as opposed to ReSharper IntelliSense).

Please note that if you’re been using ReSharper IntelliSense as a workaround in 5.1.2, as soon as you switch back to Visual Studio IntelliSense, you’ll have to initially set Auto-list members and Parameter information check boxes manually, but that is only required once.

If you’re using ReSharper IntelliSense and/or if you haven’t previously upgraded to 5.1.2, you can skip the upgrade to 5.1.3.

ReSharper 5.1.2 bugfix campaign is finally over! Please download ReSharper 5.1.2 release build (5.1.1766.4) from the official ReSharper web site. It should work well with ASP.NET MVC 3 RTM that Microsoft is releasing today.

Here’s a quick overview of fixes and improvements introduced since version 5.1.1:

• ReSharper 5.1.2 doesn’t interfere with Visual Studio IntelliSense in ASP.NET MVC 3 Razor syntax. Earlier ReSharper 5.x builds had certain issues with Razor IntelliSense that are addressed in 5.1.2. Specifically, ReSharper 5.1.2 doesn’t prevent Visual Studio from automatically providing its own IntelliSense in .cshtml and .vbhtml web pages anymore: both code completion and Parameter Info work as expected. Other than that, ReSharper 5.x doesn’t provide any additional support for Razor: only ReSharper 6 will bring full support for this view engine. Pre-release ReSharper 6 builds are currently available via Early Access Program.
• Improved IntelliSense in Watch tool windows. The Razor IntelliSense fix has a side effect: ReSharper doesn’t anymore block Visual Studio IntelliSense from automatically popping up after dot in Watch tool windows used during debugging. This fix doesn’t yet apply to the QuickWatch dialog box though.
• Live templates can now be saved one by one. Prior 5.x releases were able to save all live templates at once but, weirdly, weren’t saving them on Ctrl+S. Now you can save them one by one safely. Besides, saving templates doesn’t deselect them in the Template Explorer anymore (RSRP-90569).
• Support for Test Projects (MSTest) re-targeted to .NET Framework 3.5. We have already blogged about this particular improvement.
• A backport from ReSharper 6 allows faster processing of large files (10,000 LOC or more.)
• ReSharper PowerToys should no longer throw exceptions that they used to throw with 5.1.1.
• External Sources now reads PDB files in a better way.
• Bug fixes related to referencing CoreCLR assemblies from Silverlight projects, comments in VB.NET, BizTalk projects, shortcut persistence, and references to SharpSVN.

This is a recommended upgrade, so don’t forget to download ReSharper 5.1.2 and give it a go.

Here’s some news on the latest build from the ReSharper 5.x family.

You can download ReSharper 5.1.2 Release Candidate (build 1764) that provides support for Test Projects (MSTest) re-targeted to .NET Framework 3.5, in line with functionality provided in Visual Studio 2010 SP1 Beta.

Here’s what you’ve got to do to make ReSharper 5.1.2 RC work with this kind of projects:

1. Follow these guidelines on enabling re-targeting of Test Projects to .Net Framework 3.5 in VS 2010 SP1 Beta.
2. Copy two files, namely QTAgent32_35.exe and QTAgent32_35.exe.config, from %programfiles%\Microsoft Visual Studio 10.0\Common7\IDE to %programfiles%\JetBrains\ReSharper\v5.1\Bin.
   You’re done.

If all goes well with this RC, we’ll use it for the official release of 5.1.2 in mid-January.

We’re into another loop of 5.x bug fixing, and there’s already a couple of nightly 5.1.2 builds for you to download and try.

Why should you care about version 5.1.2? You should care about it if:

• You’re using ReSharper PowerToys and they’re throwing exceptions at you.
• You’re annoyed with ReSharper’s External Sources feature that sometimes incorrectly reads PDB files.
• You want to experience the new stunning architectural changes ported from ReSharper 6 and aimed at faster processing of fatty files (10k LOC and more.)

All these things are already there in build 1753, so go there, download it, and let us know if something goes wrong.

ReSharper 5 gets its first official update today with the launch of the new ReSharper 5.1, the bug fix and performance tuning release that additionally features support for XAML 2009.

As expected, integrating with the new Visual Studio turned out to be one of the greatest challenges for ReSharper developers. It took us 2.5 months to collect feedback from 5.0 RTM and 5.1 EAP users all around the world, reproduce integration problems and other kinds of issues, fix them, and finally come up with something that we’re ready to make an official bug fix release.

ReSharper 5.1 release brings together lots of critical issues resolved in prior nightly builds. Improvements include:

• Typing latency in ASP.NET Web Forms and MVC projects is considerably reduced.
• Markup files in in ASP.NET projects don’t lose references to code-behind files when saving files.
• No more error highlighting over good code in web projects without obvious reasons (for example, on saving files.)
• Visual Studio crashes triggered by ReSharper activity in several scenarios are diagnosed and fixed.
• No more memory leak on closing and reopening solutions in Visual Studio 2010.
• Ctrl+click (Go to Declaration) in Visual Studio 2010 now works consistently, without forcing you to click a code symbol multiple times.
• Dialogs and tool windows that use tree controls are now rendered much faster than before.
• Splitting Visual Studio text editor tabs does not hide ReSharper features in neither tab.
• Silverlight 4 support is fixed: when developing server-side and client-side assemblies in Silverlight 4, you don’t get false error highlighting anymore.
• Encoding issues are over: specifically, adding Cyrillic comments and creating custom controls in WPF projects doesn’t change file encoding.
• The locale doesn’t anymore change based on Windows locale during ReSharper refactorings.

Here’s the complete release notes.

If you’re still experiencing serious issues with ReSharper 5.1, please check against the Known Issues and Workarounds blog post to make sure that your problems are not related to Visual Studio itself or another external tool. If you’re still experiencing issues, you know where to find our bug tracker.

In addition to bug fixes, ReSharper 5.1 introduces support for XAML 2009 that includes highlighting and quick-fixes for language errors.

To illustrate this, let’s take a language version downgrade scenario: say you’re working on a WPF project where only XAML 2006 is allowed there but you’ve got a generic object from XAML 2009. First of all, ReSharper highlights the object as an error:

When you press Alt+Enter on the highlighting, there’s a quick-fix in the list where ReSharper suggests to declare a type inherited from System.Collections.Generic.List<string>:

When you apply the quick-fix, ReSharper makes two things. First, it creates a new .cs file where it declares a new wrapper type that inherits from List<string>:

Second, in the original XAML file, it deletes the TypeArguments attribute, changes the type of the object to the new wrapper type, and inserts a new namespace directive if necessary:

With this ReSharper 5.1 release, we’re closing the ReSharper 5.1 Early Access Program in order to focus on ReSharper 6 development. We’re really hoping that critical issues that affect multiple users are firmly behind us and we won’t have to reopen the 5.1 EAP.

Download ReSharper 5.1

Users keep coming with questions whether a particular issue that they encounter in Visual Studio is related to ReSharper. Well, some of them are, some of them aren’t. Either way, we try our best to provide info on workarounds for common issues, both our own and external, in this blog post. Check it out for latest updates on GetTempFileName()-related exceptions in certain versions of Windows, and “insufficient memory” messages caused by simple cut-and-paste operations in Visual Studio — both issues fortunately not in any way related to ReSharper.

As to ReSharper’s own issues, we keep fixing them in 5.1 Nightly Builds, hoping to provide the official 5.1 bug fix update really soon. If you happen to find stop-shipping bugs in the nightly builds, hurry up to report them!

A couple of weeks ago we posted a blog entry on known issues in ReSharper 5.0 and workarounds, and today we’re taking the next logical step by opening a new Early Access Program for ReSharper 5.1 to fix them. If you’ve having issues with ReSharper 5.0, please start downloading ReSharper 5.1 nightly builds: it should feel much better.

Here’s a quick list of fixes that the Early Access Program presumably brings:

• Typing latency in ASP.NET Web Forms and MVC is considerably reduced.
• Code-behind files in ASP.NET projects don’t disappear when saving files anymore.
• Splitting Visual Studio text editor tabs does not result in ReSharper features disappearing from one or both tabs.
• Silverlight 4 support is fixed: no more error highlighting when referencing Silverlight 4 code from a regular .NET assembly.
• Encoding issues when working with XAML files are resolved.

If something goes wrong, please report issues to our YouTrack project.

Hello everyone! Hope you’re having a good time using the new ReSharper 5.0. If you do, just ignore this post :)

If you’re facing issues with ReSharper 5.0, read on. There are certain bugs, usability problems and otherwise weird behavior that users report following the release (surprise!). Some of them you can work around, others you can’t, but both kinds of issues will be addressed in the upcoming ReSharper 5.1. It’s scheduled for release in June but we’ll open the Early Access Program in May, and chances are that the most annoying issues will be fixed in these early builds.

Here are some of the most annoying issues that have known workarounds:

• RSRP-178681: aspx pages lose references to their code-behind files. A lot of people complained that when saving an aspx page with a code-behind file, the reference to the code behind file gets lost and lots of errors start to pop up.
  
  Workaround: Go back to the aspx page and save it again (without changing anything): the reference restores and both files display and work correctly.
• RSRP-178492: Adding Cyrillic comments and creating new custom controls in WPF applications sometimes changes file encoding from UTF-8 to Win-1251.
  
  Workaround: The only way to change this behavior is to manually roll file encoding back to UTF-8 by choosing File | Advanced Save Options in Visual Studio.
• Another problem reported in RSRP-178492 is that during refactorings, ReSharper changes the locale of XAML files based on your Windows locale. That only happens if you don’t select the “To enable Undo, open all files with changes for editing” check box in a refactoring dialog box.
  
  Workaround: Make sure to select the “To enable Undo, open all files with changes for editing” check box.
• UPDATE! Thanks to Frans Bouma for reminding about the other annoying issue, NP-20: Splitting a Visual Studio text editor tab makes ReSharper marker bar and possibly other features go away in one or both parts of this particular tab.
  
  Workaround: Rejoin the editor tab, close it, then reopen.
• UPDATE 2! Visual Studio 2010 crashes during file save and build operations.
  
  Workaround: ReSharper may cause this problem but there’s a known common cause of this behavior: a certain version of AnkhSvn. If you have both ReSharper and AnkhSvn installed, try following Microsoft guidelines on updating your AnkhSvn build. Builds 2.1.8420 and higher are reported to fix the intermittent Visual Studio crash problem.
• UPDATE 3a! RSRP-147892: Calling GetTempFileName() in Windows 7 or in Windows Server 2008 R2 causes UnauthorizedAccessException
  
  Workaround: This is not a ReSharper problem. Microsoft has confirmed that this issue occurs because the GetTempFileName() function in Windows 7 and Windows Server 2008 R2 handles a duplicated file name incorrectly. Download this Microsoft hot fix to remove the issue.
• UPDATE 3b! Even small cut-and-paste operations raise “insufficient memory” errors in Visual Studio 2010.
  
  Workaround: Again, this is not a ReSharper issue. Microsoft has released a patch for Visual Studio 2010 that removes this issue. For details on its symptoms and other implications, read this Visual Studio blog post.

We also receive reports about performance issues when renaming and doing Find Usages in large projects that contain aspx files. We are doing performance analysis and aiming to solve these issues in time for the bug fix release.

Just in case you’re interested, here’s the full list of issues currently scheduled for ReSharper 5.1.

On a different note, people report on a regular basis about Visual Studio 2005 or 2008 installations that freeze or crash after opening web forms, or Solution Explorer that hangs up. There are known solutions to this kind of issues (not having anything to do with ReSharper), including:

• Removing Microsoft Visual Studio Web Authoring Component,
• Reinstalling Microsoft Office 2007,
• Removing Communicator 2007 and LiveMeeting 2007.
• (Update!) Uninstalling KB976569, installing KB974417 and reinstalling KB976569.

Before you contact us with such issues suspecting ReSharper, please make sure to try the solutions provided above.

By the way, if you’re using Visual Studio 2010, have you installed Windows Automation API? Rumors say it really boosts Visual Studio performance, particularly with ReSharper.