I wonder what the resource usage of this will be. ReSharper with C# really slows things down on my machine. With an SSD it's fine, but with a regular HDD I notice the difference.
(these are all from a recent reddit thread: http://www.reddit.com/r/programming/comments/31xbrt/jetbrain...)
Seems that it depends on the size and complexity of a solution, takes trying to see if it's acceptable in a given environment. That said, a lot of performance work is ahead provided that the team has input on what's going wrong and in what circumstances.
Just some statistics on my setup:
Machine: i7, 8GB RAM, 7200 rpm HDD, vs2012 (upgrade to 2013 happening soon hopefully).
Project: 70 Projects in Solution, ~500k LOC.
I tried it again today and it was simply too slow for my taste. The HDD on my machine needs to be replaced, though, so it isn't all on Resharper. I suspect with a proper SSD it wouldn't be nearly as slow.
I haven't tried it for C++ solutions.
Our project is starting to go that direction (we're using areas in MVC). Is there any tricks you've discovered to manage better with that many projects in the solution (e.g. have the projects in the solution but unopened or something)?
PS - Yes, there is a giant hack to build areas as a stand-alone binary, but it is clunky and terrible. Hopefully the MVC team add first-party support in the next version.
I'm not affiliated with them in anyway, but I am a huge fan.
It appears like Visual Studio 2015 has many of the Reshaper features I most covet, and doesn't appear to have the same performance issues (likely because they're powered by architecture changes), so win/win, and I save $149 since my employer gets us MSDN.
ReSharper makes writing C# a lot easier so I stick with it.
VS2015 has, on paper, some of ReSharper's features but I tried it without ReSharper and it felt ... dead. So you still need it for a complete C# IDE experience.
Okay so some big companies haven't yet gotten around to upgrading, but a) there are going to be fewer of those around and b) this is a new tool. It is not necessarily a bad idea to target your tool a little in front of the average machine, especially if you want to be the best.