ReSharper 5.0: Known Issues, Workarounds, and Bugfix Schedule

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:

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.

image description