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.
Mixed comments on resource usage so far. Some examples:
* "Besides beeing a bit slow, VS suddenly felt like a proper IDE"
* "a bit more sluggish than using vanilla VS, but made up for it in terms of usability"
* "even after I've opened the project and everything is parsed, Visual Studio slows down too much for it to be acceptable"
* "once resharper had completed (warning up) though, everything was fine and Visual Studio + performance was pretty good"
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.
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.
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 think it should definitely get better with SSD although not sure if it would be completely OK: 500k is quite a lot, at least by v1.0 standard. Give it a try when/if you're on a SSD. Do get in touch with us (https://youtrack.jetbrains.com/issues/rscpp) if still too slow by then, we'll try to see what can be done.
I had to uninstall one of the later beta builds because leaving any C++ Visual Studio solution open would result in a massive multi-gig memory leak. VisualAssistX is still installed because it's lightweight and though it doesn't have the same featureset as ReSharper, it doesn't get in the way. Don't get me wrong though, I'm still willing to try RS again.
You should consider CodeRush from DevExpress. They've always been super serious about performance (they have perf stats on their site). They've had C++ tooling for years, their UI is top notch and their live templates blow R# out of the water.
I'm not affiliated with them in anyway, but I am a huge fan.
That's exactly why I uninstalled Resharper. I loved the extension, and was quite seriously considering paying the cost of admission ($149), but it just dragged down Visual Studio 2013, both in terms of start times and I also had random second-long freezes throughout the day. This disappeared as soon as I uninstalled it.
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.
I always thought Visual Studio was a dog but one day I opened it with ReSharper disabled and it was blistering fast.
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.
Second-long freezes... could be ReSharper, could be a different plug-in or a VCS integration interfering with ReSharper. Unfortunately you got rid of it so I guess we'll never know for sure )
They said when they got rid of it the freezes disappeared. So I guess we do know. I too have experienced period freezing with ReShaper so none of this really surprises me to read (in particular if you have a HDD).
I am not sure it matters much anymore - why would you want to get a computer without an SSD?
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.
I haven't used a non-SSD in a dev machine for over 5 years. Sometimes people in the office fill their SSD C-drive and start working from D-drive. This is unacceptable and they get a bigger SSD.
