Yesterday Microsoft released the RC (Release Candidate) for Microsoft Visual Studio 2012.
You’ll be happy to know that the latest ReSharper 7.0 EAP builds work with Visual Studio 2012 Release Candidate!
Specifically, at the time of publishing this blog post, build 59 is known to be working well with the RC, and subsequent builds should run nicely there as well.
Judging by our internal tests, using fresh R# 7 EAP bits with VS 2012 RC should be a relatively smooth ride. However, there’s a bunch of known issues. First, you could get false error highlighting in newly created Razor web sites. To work around this, just let ReSharper explicitly import the namespace that is considered implicit starting VS 2012 RC. Second, false error highlighting is also possible in newly created web applications. This can be worked around by typing some code in the affected file and saving it, which would cause the corresponding designer file to be re-generated, and the problem should go away.
On another note, in Visual Studio 2010 and below, latest ReSharper 7 EAP builds don’t live together well with TeamCity add-in for Visual Studio.
If you happen to face other issues, please report them to ReSharper issue tracker or use the ReSharper Misbehaves button in Visual Studio toolbar. If you happen to experience performance issues with ReSharper 7, we have a new recipe for reporting this kind of issues to us — read on.
Reporting Performance Issues
Although we will be covering the new features for ReSharper 7.0 closer to the release, there is one important thing we’d like to mention, specially during this EAP program. Under the Help menu there are two new entries:
To make it easier for you to send us information about performance issues you might be having, we have bundled dotTrace Performance core with ReSharper that makes it extremely easy to gather performance data and provide it to us for investigation.
If you have any type of lag with ReSharper, select Profile Visual Studio. It will automatically attach itself to VS and start profiling, launching the dotTrace Controller window
You can continue to work until you feel enough time has passed for the performance degradation to be apparent. Once ready, click on Get Snapshot. It will then prompt you to see whether you’d like to send us the information directly via FTP or open it in dotTrace Performance. Note that in order to analyze it yourself, you need to have dotTrace 5 Performance installed. This is also required if you pick the Profile Visual Studio and Open Snapshot option.
Once we have this information we will get in touch with you and hopefully sort out the problem. Once done, make sure you detach dotTrace Performance from Visual Studio in order to not further impact performance, by clicking on the Detach from Process button.
It is also important to mention that our tests show that ReSharper 7 is even faster than 6.1 and more so in Visual Studio 2012 RC, so hopefully you won’t need to use this feature much!
Bonus: What’s Coming in Themes
Although not available in the current EAP, in one of the upcoming builds we will be providing themes for ReSharper to align with Visual Studio’s new looks. As good citizens of our host, Visual Studio, ReSharper icons can optionally be themed to fit in with the new VS2012 look.
This is applicable both in context menus as well as other places such as the Options dialog:
We will also be providing support for the Dark Theme of Visual Studio. Some things are already supported but not everything, so don’t be shocked if you see gray fonts on black backgrounds. It will be fixed!
The download page for ReSharper 7.0 EAP has not changed, so you grab ReSharper 7 builds for Visual Studio 2012 RC from a familiar. Of course, the new builds are also supposed to work with other Visual Studio versions, namely Visual Studio 2010, 2008, and 2005.
Download the new bits, have a play and let us know!