ReSharper and Visual Studio: Where do We Stand

Visual Studio keeps evolving, and ReSharper support for the Microsoft IDE is up to the challenge as usual. As a reminder, ReSharper 8.x currently supports a staggering 5 Visual Studio versions: 2005, 2008, 2010, 2012, and 2013. It’s only been half a year since we discontinued sales of ReSharper 2.x with support for Visual Studio 2003.

In light of recent Microsoft announcements and our internal decisions we’d like to give you an update on how we stand in regard to supporting different versions of Visual Studio. We have good news and bad news.

Bad news: ReSharper 9 and other .NET tools will not support Visual Studio 2005 and 2008

This was coming for a long time but we kept giving VS2005 and VS2008 one last chance after another. It didn’t help the case that certain recent ReSharper features such as Architecture Tools and Extension Manager weren’t by definition compatible with VS2005 and VS2008. Given the complexity of changes that ReSharper and other .NET tools have been subject to during the ReSharper 9 development cycle, we could have opted to release unstable, untested support for VS2005 and VS2008 but we chose not to. As we stand, we have to stop maintaining support for these releases to focus on up-to-date challenges.

To sum it up, the upcoming releases of ReSharper (including ReSharper 9) and other JetBrains .NET tools will not support Visual Studio 2005 and 2008. Only Visual Studio 2010 and later will be supported further on.

ReSharper 8.2.3, dotTrace 5.5.6, dotMemory 4.1 and dotCover 2.7.2 will become the last releases to support Visual Studio 2005 and 2008. Please keep using these stable releases if you’re staying with Visual Studio 2005 and/or 2008.

Should you or your team mates need to purchase new ReSharper licenses and expect them to work in Visual Studio 2005 and 2008, as a workaround, you’ll be able to buy ReSharper 9 licenses and use them with ReSharper 8.2.3 as we have specifically made sure that this release accepted the new license format.

Good news: ReSharper 9 will support Visual Studio 2015

Therefore, ReSharper 9 will support Visual Studio 2010, 2012, 2013 and 2015.

Following the pattern of ReSharper 8 release, version 9.0 will provide support for Visual Studio 2015 Preview, and further updates will add any necessary improvements required to integrate smoothly into the final VS2015 release. In case you have missed it, the current early ReSharper 9 builds work with Visual Studio 2015 Preview although there are known issues with its dark theme that are going to be fixed shortly.

We’re also close to smoothly integrating ReSharper’s quick-fixes and other Alt+Enter actions with Visual Studio 2015’s quick actions in a single UI:

We expect to write more about ways how ReSharper 9 is going to work in Visual Studio 2015, so stay tuned.

More good news: Both ReSharper 8 and 9 integrate with Visual Studio Community 2013

Microsoft has recently released the (conditionally) free Community edition of Visual Studio 2013 that totally beats Visual Studio Express by supporting extensions. Immediately we were faced with questions whether ReSharper would work in the Community edition. The answer is yes, both ReSharper 8 and ReSharper 9 do integrate into Visual Studio Community 2013.

The next question we faced in this regard was whether ReSharper would introduce a free edition as well. Well, we’re not planning to provide a special free edition. This is not necessary however. Similar to Visual Studio Community that is only available to specific groups of customers (see Channel 9 Q&A for details), ReSharper is also available for free to multiple groups including Microsoft MVPs (along with other JetBrains .NET tools and WebStorm), students and teachers (along with all other JetBrains products), as well as faculty members and trainers for use in classroom environments. Additionally, startup companies can enjoy a 50% startup discount on all JetBrains tools.

This entry was posted in How-To's and tagged , , . Bookmark the permalink.

40 Responses to ReSharper and Visual Studio: Where do We Stand

  1. MichaelD! says:

    NO WAY should you make ReSharper Free!!! Especially now! Having the same IDE as the Ultimate Edition for FREE means that every developer has all sorts of theoretical budget to spend on ReSharper’s value. :)

    • Julio says:

      Yeah especially those living in third world countries.

      • Bunny Charles says:

        Julio, I think your comment is not fair and shows lack of maturity or knowledge. It is not just third world countries that look for a lower price. In fact, outsourcing happens because somebody somewhere wants to cut costs. This is evidently looking for skilled people who can work at lower cost – not because it is actually lower. The lower cost is actually highly paid in that country – it’s just a thing of the stock markets.

    • Oisin G. says:

      The Community Edition is not equatable with Ultimate: It has approximately the same functionality as Visual Studio Professional.

    • Sean says:

      How dare a better developer, do the same work as me in less time (and less money) using a tool like ReSharper right? If you have to worry about someone developing better software than you using ReSharper (If they give it for free) then the chances are you’re not a half decent dev your self. I’d reskill or find a different career if I were you.

  2. Daniel Abbatt says:

    I think a “free” version under the same logic that MS provides VS “free” edition would be good. i.e. companies with 5 or less developers could use it. That way you get the developers hooked into using it and when they go to a bigger company or the company grows then the culture will be to use the tool, which will then be paid for. Even then, keep it low cost and it’ll be a no-brainer to install on every developer’s machine.

    • Any business serious about development would gladly pay the $349/seat plus yearly maintenance for Resharper, whose productivity enhancements alone make it a bargain at that price.

    • Seth Earby says:

      Or independent developers who are currently not using ReSharper for their job. If they have the ability to full use it and come to the workplace and give a valid review on why this is necessary. If a developer uses this product and can vouch that it did make them more productive and it should be used in the workplace that can be invaluable for JetBrains.

  3. Pingback: The Morning Brew - Chris Alcock » The Morning Brew #1742

  4. Pingback: Dew Drop – November 21, 2014 (#1901) | Morning Dew

  5. Bad news: ReSharper 9 and other .NET tools will not support Visual Studio 2005 and 2008. THIS IS NOT BAD NEWS!

    It is entirely unreasonable for you to spend effort down porting Resharper 9 to products that are nearly a decade old. This is the same nonsense that some companies support IE6 and IE7.

    You have great products for these old tools, there’s no reason to try to bring every new feature back to them. Even further, how many of these features wouldn’t even be relevant?

    I’m glad to see you’re not supporting these copies of Visual Studio.

    • Ken Sykora says:

      Heck, It’d make sense if they dropped support for 2010 too.

      • Jeff Klawiter says:

        Personally my heart sank a bit. Having to occasionally support Windows Mobile applications requires using 2005 or 2008. Thankfully it is possible to have older versions of R# installed, just have to make sure to install them in the correct order and keep track of old licenses.

    • Per Erik Stendahl says:

      It is definitely bad news. I’m working on a pretty big WinCE 6 application written in 3.5 CF and VS2008 is a requirement since newer versions of Visual Studio don’t have support our devices. Having R# in VS2008 is keeping me sane. =)

      • Jura Gorohovsky says:

        Hi Per Erik,

        I feel for you but fortunately you can still use R# 8.x generation on VS2005/2008. An added bonus is that 8.x is pretty stable after 1.5 years of maintenance: something that 9.x is yet to achieve.

    • James Pattison says:

      Unfortunately “Don’t support ie 6 or 7” isn’t quite as achievable as you would think. Big companies like banks are very unwilling to change any software having security in mind (daft, i know, but income outweighs logic in these situations)

  6. Pingback: 1p – ReSharper and Visual Studio: Where Do We Stand – RunWhere.com

  7. Robert Mircea says:

    Any plans for a .NET/C# Jetbrains IDE for Mac giving the recent announcements about ASP.NET going free and compatible out of the box with Mono on Mac?

    It would be a bold and a tremendeous business move given the availability of so many Jetbrains products on Mac which should provide a solid foundation for a C# IDE. Many developers try to use Xamarin Studio, but any IDE from Jetbrains running on Mac is by far superior.

    My ideal setup would be developing C# apps (ASP.NET or headless servers) on Mac and running them on Linux servers.

    • Jura Gorohovsky says:

      Robert, we’re still not planning a C# IDE.

      • Ken Sykora says:

        You guys should though! You really should.

      • However Jura, you REALLY REALLY should. Jetbrains alone is holding the key to unleashing a feasible development environment for .NET on Macs.

        I’m sorry, but MonoDevelop / Xamarin Studio DOESN’T cut it!

        I can tell you the whole world of innovation (startups/agencies/modern companies) has moved away from Windows in hordes and server developers on Mac everywhere are held back from getting into the fantastic C#/.NET ecosystem because they don’t have a feasible way of building C#/.NET on OS X.

        There couldn’t be a better opportunity to kick off a .NET product on Mac and monetize off this unique opportunity. With the announcement of Win 10, it is evident Microsoft is not fixing their design language problems anytime soon (which is what has plagued their adoption of Win 8, and now continues into the era of Win “10”) which means they will not be winning back market share of user adoption anytime soon for the forseeable next few years – and in fact will continue to shed it to the fantastic Mac/OS X ecosystem.

        NOW is the time for having a C#/.NET IDE on the Mac. Please announce your plans that you are working on it already, so we can rally up the support behind it internally in our companies, throughout the communities, and head for a fantastic release that it would so rightfully deserve.

        Seriously!!

  8. Pingback: Les liens de la semaine – Édition #107 | French Coding

  9. Kamran Ayub says:

    It would at least be nice to support a R# for OSS developers; it sucks when multiple devs working on maintaining an OSS project own R# but some don’t; so settings don’t get honored when non-R# devs work in Visual Studio (things like naming, formatting, language settings, etc.).

    However, I have no idea how you’d ensure it only gets used for OSS development (I guess the same way you can’t know if VS community gets used for commercial dev).

    • Jura Gorohovsky says:

      Kamran, ReSharper and most other JetBrains tools have been available to non-commercial OS project for years, and over 1500 OS projects have qualified for free ReSharper licenses alone. Check that your OS project meets our OS program criteria; if it does, ask your project lead to apply for an OS license (to be renewed once per year.)

      Whether it’s used for OS development, we can’t really check this all the time but we trust that OS developers comply with the license agreement that they become subject to once they start to use the OS license.

  10. Jerry Nothstine says:

    I just downloaded the ReSharper 9.0 beta version and it doesn’t seem to support the new C# nameof operator. When I use it, ReSharper identifies it as an error, even though my code compiles. Is there a setting that I am missing or is it just not supported yet?

    • Alexander Shvedov says:

      Hi, Jerry. Unfortunately, two features of C# 6.0 – nameof() and string interpolation expressions – are out of C# 6.0 features scope supported in ReSharper 9.0. This is simply because language features design and syntax isn’t stable enough by now. For example, recent changes allow nameof operator to accept limited forms of expressions like nameof(this.someField) (only references of the form nameof(ShortName) or nameof(Type.Member) were allowed before). Proposed changes for string interpolation syntax ($"id: {someId}" instead of "id: \{someId}") are not implemented yet in ‘master’ branch of Roslyn compiler.

      When C# design details will be clarified enough and compiler implementation will be available, we finish the nameof() and string interpolation support and ship it with ReSharper 9.1 EAP (we expect 9.1 EAP start few weeks after 9.0 release).

  11. Arne Evertsson says:

    I need to use Visual Studio 2008 for projects that target Windows Mobile. Will it be possible to keep ReSharper 8 installed in VS 2008 while using ReSharper 9 with the latest VS version?

  12. Mark G says:

    Just discovered that VS2005 no longer works :-( We have projects in 2012 and 2005, and want to go forward AND still have an old resharper for the old studio.

    Sadly there is no way for two versions to coexist. I can’t even find a link for the last version of the command-line tools which worked with VS2005.

    I understand that you can’t support old versions forever, but you can ease the pain by making it so multiple versions could co-exist.

    • Jura Gorohovsky says:

      Mark, to clarify, do you actually need ReSharper Command-Line Tools to work with VS2005, or ReSharper as Visual Studio extension?

      Also, ReSharper 8.2.3 or earlier can be perfectly installed in VS2005 and VS2008 while the later versions of Visual Studio have ReSharper 9.x integrated in them.

  13. Martin says:

    Will there be a Resharper 8.x which is compatible with VS 2015?

  14. Abhimanyu says:

    Can Resharper 8.2.1 support Visual Studio 2015 ???
    or is it mandatory to go to ReSharper9 in case i am migrating from Visual Studio 2013 to Visual Studio 2015

    • Jura Gorohovsky says:

      ReSharper 9.2 is the first release that works with the initial release build of Visual Studio 2015.

      However, since Visual Studio 2015 is currently at Update 1, using ReSharper 10.0.2 is highly recommended.

Leave a Reply

Your email address will not be published. Required fields are marked *