|
Why not just uninstall it completely?
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
|
|
|
|
|
Precisely my solution.
The instructions don't disable all of the functionality though - there is a lot of stuff about navigating class hierarchies I used to find useful, but since the latest upgrade the performance has been pants.
|
|
|
|
|
I haven't used it for years.
do you know if it allows you to navigate from a XAML to a viewModel at all? (i.e. is there a 'go to definition' equivalent from the Xaml View to a property in a Viewmodel?
That would be useful - although I'm not sure how it would do it!
PooperPig - Coming Soon
|
|
|
|
|
No idea I'm afraid - rarely use XAML nowdays.
|
|
|
|
|
I often wish I didn't 
PooperPig - Coming Soon
|
|
|
|
|
"I often wish I didn't"
I sometimes think I'm glad I didn't (ever use it), but, then ... I don't know what I've missed, do I ?
|
|
|
|
|
It's one of those things, I think, that I would have become an expert in, in my youth, and told everyone how wonderful it was - then slowly, over the years, realised how much energy I had put into becoming an expert in something that really isn't going the distance.
That it is a clever idea is undeniable.
That it was implemented poorly is likewise undeniable.
Another one of those things that, had they kept it behind closed doors for a few more years, while they stress tested it, made it easy to use, with tools and smarts, it could have been awesome.
But its not!
PooperPig - Coming Soon
|
|
|
|
|
well you should get used to it as VS2015 has a virtual clone of it.
The main difference is that VS 2015 has access to the VS compiler whilst R# has to use its own (a major part of the slowness)
You cant outrun the world, but there is no harm in getting a head start
Real stupidity beats artificial intelligence every time.
|
|
|
|
|
Keith Barrow wrote: but since the latest upgrade the performance has been pants.
I have the latest release and I have not had any issues with performance. All my settings are there, I have not had to disable anything. I would look at the performance of your PC/laptop before accusing ReSharper. Just saying.
|
|
|
|
|
I'm not running ReSharper at all and it never bogs down my machine, so I believe uninstalling does make it as fast as possible. 
|
|
|
|
|
Not to speak of the time you save not having to undo what that thing does when it thinks it knows better than you what you are about to type.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
|
|
|
|
|
This is funny. I basically got called an idiot on someone's article where he said he wouldn't hire someone if they didn't use R#. I pointed out that projects of any complexity generally render R# unusable and R# renders VS useless. Apparently I'm stupid.
|
|
|
|
|
I can't imagine how slow R# would make VS these days, esp. using Xaml - it runs like a pig at the best of times (although 2013 is a huge improvement!)
I kind of see where they might be coming from with their 'performance advice' though - I probably only used 1/10 of the features when I used to use it - so if turning off the 90% I didn't use made the 10% I did useable, it would be a great thing!
I think if someone genuinely said they wouldn't employ anyone not using R#, I kinda wouldn't want to work for them anyway! It's kinda like demanding an artist uses a particular make of brush to paint a portrait - or a brand of camera to take a photo - or -= you get the idea - it's dumb!
PooperPig - Coming Soon
|
|
|
|
|
One of the best devs we've employed at my workplace refused to use it - citing the performance as a big thing.
I tried it in 2006, and again in 2008 and found it unusable and unstable both times. When I started at tombola (in 2012) almost everyone used version 8 -I was sceptical, but tried it and the performance was acceptable if not brilliant. Then they release version 9, and the old problems re-surfaced. TBH most of the more useful features seem make it into the next VS release anyway, sans performance probs.
It'll be interesting to see how Roslyn affects the VS IDE - JetBrains have already said they won't use it.
|
|
|
|
|
I'm sure someone told me it would allow navigation between view and viewmodel - which IMHO at my current place of work would be worth its weight in smack!
I don't see how that would work - but ay improvement n Xaml handling would be good!
PooperPig - Coming Soon
|
|
|
|
|
Had someone try to convince me to use it once, all it did was turn me into a grumpy old git.
Every day, thousands of innocent plants are killed by vegetarians.
Help end the violence EAT BACON
|
|
|
|
|
So that's what happened!
PooperPig - Coming Soon
|
|
|
|
|
I am a fan of ReSharper, and consider it one of the best software tool purchases I ever made.
I note that the link you provide ... from JetBrains ... is a very detailed, and thoughtful, analysis of many settings that can be used to tailor the behavior/use-cost of R#. I think that, in itself, is an indicator of concern for developers, and responsiveness to their issues.
I feel it is very appropriate for a specialized tool for programmers to provide myriad features, and to expect a reasonable investment of programmers in investigating those features, and deciding which ones they need in a given development context !
Yes, it can be slow when dealing with very large projects, but I am not sure if that slowness may be caused more by Visual Studio 2013 than R#.
From my point of view, "worst case" is you just disable/pause R#; you can do that for selected files, the current file: or, to take R# off-line for the current Project : context-click on Green R# icon at screen lower-right, select "Stop Solution Wide Analysis" ... then turn it back on again when you wish.
I do notice that on my new system (i5-4670k, Z97 motherboard, 16 gigs of ram, Samsung 850 128 gig SSD for primary drive) using VS 2013 with R# 9 (latest release, not EAP) runs a whole lot faster.
I am also very impressed with JetBrains' quick and detailed responses to any R# issue I have raised, or question I have asked.
cheers, Bill
«I'm asked why doesn't C# implement feature X all the time. The answer's always the same: because no one ever designed, specified, implemented, tested, documented, shipped that feature. All six of those things are necessary to make a feature happen. They all cost huge amounts of time, effort and money.» Eric Lippert, Microsoft, 2009
modified 18-Feb-15 16:07pm.
|
|
|
|
|
BillWoodruff wrote: Yes, it can be slow when dealing with very large projects, but I am not sure if that slowness is more caused by Visual Studio 2013 than R#.
That's just it - Suffering masses of lag with resharper. Uninstall and suddenly it's all OK again. Some people at work have even downgraded from v9 to v8 (the performance on v8 was OK when I used it).
|
|
|
|
|
Hi, Keith,
Of course, I respect your substantial experience. If R# ain't for you, that's no bacon off my hog's loin 
However, I do think it's fair to ask if you have explored most of the settings available with R#, and "tailored" it to your needs, and, if so, if have you seen a noticeable improvement in speed related to R# alone.
One reason I skipped investing in learning/using WPF was the (for me) horrible experience I had using it in Visual Studio (and the reports of other devs on how slow it was, and, later, the uncertainty about its future viability) ... and my allergic reaction to XAML ... but that was years before I purchased ReSharper, perhaps even pre- Visual Studio 2010 (?)
cheers, Bill
«I'm asked why doesn't C# implement feature X all the time. The answer's always the same: because no one ever designed, specified, implemented, tested, documented, shipped that feature. All six of those things are necessary to make a feature happen. They all cost huge amounts of time, effort and money.» Eric Lippert, Microsoft, 2009
modified 18-Feb-15 16:06pm.
|
|
|
|
|
I have never had a problem using ReSharper. You need to have the latest release, because the older ones did have issues. You also need to have a reasonably powerful computer; which you should have anyway, if you are going to developer software.
|
|
|
|
|
That's just it - v8 was actually OK and I used it for a couple of years, v9 just makes things grind.
|
|
|
|
|
are you running VS2015?
You cant outrun the world, but there is no harm in getting a head start
Real stupidity beats artificial intelligence every time.
|
|
|
|
|
|
I am running 2012 premium. This may be a compatibility issue with higher versions of VS, maybe?
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
