Derik Whittaker

It's painful.  And why does it suggest that you use implicitly typed variable for everything local?

Oh and I'm targeting 2.0 framework in one project and it suggest c# 3.0 refactorings everywhere.  Nice.

I love Resharper but someone needs to put boot to ass and get it back on track.

I'm getting tons of OutOfMemoryException, everytime I type a { or } in javascript it takes forever to parse the page.

I understand that R#4 is still a nightly build... I guess they should do some serious refactoring to make the application less memory hungry

I think I'll go back a few "works here" version..

Also, they stopped answering on the EAP forum as well... what's happening out there?

You've been kicked (a good thing) - Trackback from DotNetKicks.com

Indeed, many exceptions in the latest build.

Hey guys, don't release a build if you don't run some sort of validation on it.

I haven't tried the beta yet, I don't like living on the bleeding edge.  I do love Resharper.  It's way better than the next closest offering from DevExpress which seriously drags my system down to the point it's unusable.  Anyway, as far as wanting the Resharper folks to hurry...  When it comes to software, you can have only two of these three things:  Quick, Cheap, Good.  If it's quick and good it wont be cheap, if it's cheap and good it wont be quick, etc.  Complaining about the quality of a beta product is useless.  It's beta people.   If it's not good enough for ya, be patient and wait for the release version.

Alan,

Every language change in C# 3.0, except for Linq and expression trees, can be used in a 2.0 project.

If you are using VS 2008, then your project files are already unreadable from 2005, so it should suggest the 3.0 language enhancements that are compatible with the 2.0 runtime.

I think it's a real shame. As a lead dev on CodeRush and Refactor from DevExpress, I'm obviously biased. However, I think Resharper is a really great tool, and JetBrains has done their customer base a disservice. It wasn't like the release of VS 2008 caught JetBrains by surprise. Everybody knew when it was coming, and after 5 months, it's clear that they weren't even close to ready.

I've spoken with several alpha developers that are actually staying away from LINQ because Resharper isn't there yet. IOW, allowing the tool to direct their technology choices. Very sad.

It is taking an unusually long time for them to finish this one off.

That being said, it is an EAP release, so like you stated above, if you are willing to brave an EAP I think there is little room for complaints =)

Not to say I don't enjoy reading your complaints, but you get my point.

I don't think I'll move away from R# because of pre-alpha version that are not working very well...

But if you (jetbrains) decided to jump in the EAP game, you have to understand that you have to provide feedback to the users that are helping you shape your product for free... you cannot just ignore the feedback.

It is true that is annoying that it isn't release yet but if you want to be on the bleeding edge and run R# 4 then understand that this is their own nightly builds - it is not even EAP builds as we know and love them :-)

I couldn't live without R# 4 - even in its current state...

I'd be interested to hear what is lacking in coderush that would prevent people using resharper 4 EAP to make the switch.....

Bryan, I'll take quick and good please!

Quite frankly it's a bit of a joke. I know they had to rewrite a lot (thats the picture I got from the blogs etc) to support the new features - but this wasn't a surprise, I can't remember how long some form of the C# 3 and VB 9 specs have been out (in some form or another - certainly since VS 2008 Beta 1).

I can't imagine me getting Resharper 5 if it is the same again.

Also (yes I know its still a pre-beta) R# 4 is slow as hell on startup and my machine isn't exactly slow. I was seriously considering removing it yesterday as it is really annoying me now, takes 30 seconds to spin up when I open a project - touches non C# projects as well (e.g. C++? can't seem to turn it off!!!).

Not a happy bunny.

I don't think the complaint is that it's beta software, it's the fact that it's *still* in beta almost half a year after VS2008 has been released. Which might be understandable had VS2008 not been available in beta itself for so long. There's no reason they couldn't have had a version, *any* version ready right off the bat when VS2008 came out.

I agree that this has little to do with the quality of the builds, and more to do with the quality of the builds almost 6 months after VS2008 was released. If the EAP's were at this point on release, then there would be nothing to complain about.

On a side note, I too have reverted to version 767, since any of the later versions just crash constantly.

JetBrain's bug tracker for their ongoing development of ReSharper 4.0, www.jetbrains.net/.../11304, currently states that "3594 of 5443 issues have been resolved".  1635 issues are currently open, of which 228 are Major, 90 are Critical and 29 are Blocker.  From this I glean the following: (a) The RTM version won't be out very soon, and (b) only an *idiot* would want them to just declare it "done" and put it out there right now.   I'm currently using 3.1 and ignoring incorrect warnings - the one main thing that's been stinging me is crashes when editing CSS.  Otherwise I'm still getting lots of benefit while I wait...............

I'm a CodeRush/RefactorPro user myself, simply because that's what my organization purchased before I was hired. I love it and think it's a great product, but I'm constantly reading about people that love Resharper.

Like Josh, I'm curious: what does Resharper do that the DevExpress offerings do not?

I've gone back to 3.1, even for targeting 3.5 framework. 4.0 was crashing too much and the final nail was when my colleagues VS installation became unusable (couldn't even uninstall) after installing R#4.0.

Derik, the unit test runner is available as a separate download from jetbrains, Resharper is not required.

serves you all right for using code crutches like this. Learn how to code and use the IDE properly and you dont need them.

I am using the R# 755 build without any major problems (for almost a month) on a fairly big code base

You can turn on red/gring/yellow in CodeRush too.. Check out the Options\Paining\CodeIssues (If I remember well that was the option)

If you want to use Code Issues in CodeRush, obtain latest daily build from Mark's team. Last official one was released in december 2007 and this feature is VERY buggy in those release (I think it is still beta feature).

@Nikola, @Przemyslaw:

Yes, the Code Issues are working better in newer builds (gearing up for a new release soon!), but they lack the maturity of Resharper's. However, once this is rock solid, we'll be adding code issues as an alarming rate.

I think the UI for RefactorPro/CodeRush completely annihilates R#. Its biggest drawback is that it doesn't do real time code analysis, but they're working on it! Right now the 3.0.5 version has a "Code Issues" option, but it only shows things like unused variables and non-existent method calls.But they're working on expanding those features.

I am curious as to who will release a new version first, the upcoming Code Analysis features that will be released from Developer Express, and the reaction of the .NET Developer Community.

- When you mention latest build, do you mean latest "working here" build or latest build?

- R# 4 is beta so don't be complaining about its stability. Yes it's taking a long time but so is Coderush's code issues. This might be a complex piece of software to develop. What's wrong with using R# 3.1 or because it doesn't support .NET 3.5?

- CodeRush is also taking FOREVER to get their code issues working. As of just two weeks, this feature is just useless. I have mentioned this in their forum. community.devexpress.com/.../63936.aspx. No comment from them.

- DevExpress has been promising the code issues feature for years so I can tell you that R# is way ahead in the code analysis field.

- Look at Jetbrain's bug tracker and you'll find they are fixing issues every day and making this visible to everyone. I don't think DevExpress is doing the same.

- I get the feeling DevExpress makes a lot of promises and rushes to put products in the market with many missing features. They released their html editor recently and it's a JOKE. It doesn't even support inserting tables and form elements. Every html editor in the market does this basic thing. As a developer, I will be ashamed to release a skeleton product like that. Give me one reason why I should purchase such a product. Telerik's and Cutesoft's similar products are years ahead in feature base.

- If you're big into refactoring, look at Refactor. Personally I use fewer than 10. I love R#'s code analysis.

I think you are expecting too much from the nightly builds. You call it EAP, but they haven't tagged any of these releases as EAP ready yet. Check the legend on the EAP page. Once they determine a build stable enough for general consumption, they mark it as an EAP build and post it on their EAP page.

You are complaining about bugs in pre-alpha software. You should be happy that they even release their nightly builds. Most companies wouldn't let you touch alpha code just in case it gives you a bad impression like this seems to have done for you.

If people continue to complain like this, fewer companies will give us the opportunity to test their nightly builds.

I have been using build 767 without any major issues for a while now and I am very happy with it. I occasionally have to restart visual studio but thats about it.

"The simple fact is this.  Regardless of state or version.  If something is released to the wild the company must EXPECT both complaints and complements."

They are expecting this. You can post your complaints in their forum. Did you do that? Did you contact them directly?

If you're complaining in your own blog only, that's not good enough.

What do you suggest they should do.. hire more developers?

To respond to two previous posters about CodeRush vs. R#, there are a couple of main reasons why after having used both I currently prefer R#:

1) Real-time code analysis.  Having squiggles and the error-bar along side is outstanding.  Also having dead/redundant code greyed out is extremely helpful.

2) Some of the navigation features are better.  While CR now has some of the features R# has, being able to Ctrl+T to get a type is easier than the current CR shortcut to do the same.

3) This is "easy" but I use it all the time -- Ctrl-clicking variables/types/methods in code to go to declaration.  It's much easier than right-clicking and selecting the option.  It's like turning your code into a huge hyperlinked thing.  I say "easy" since the Ctrl-click is really just calling VS's built-in Go to Declaration function.  CR -- please add this?

3) Code reformatting.  R#'s has a ton of granularity when it comes to code formatting.  There's also a cleanup function that allows me to "var-ify" code, turn stuff into auto-properties, reformat, etc.

4) XAML.  Does CR's refactoring support symbols in Xaml yet?

Lastly, some of the CR interface seems too "in your face".  The dialog that comes up in the lower-right of the screen is annoying...

All that said, if CR has a version that addresses these, then I'm all for trying it out again.

Pingback from  Head.SmackOnTable();  » Blog Archive   » Refactoring Made Easy with Resharper 4.0

You must be unlucky, I have 4 machines all on R#4 of some build or other (I update now and then, but not religiously) ... and rarely have any problems these days ... I did find one reproducable bug last week, but it was so minor it wasn;t a problem ...

So, how is that RTM coming, you ask?  Ok, you didn't, but I'm here to depress you anyway!!  Let's review the bug tracker stats from before, then compare them to today!

Resharper 4.0 Issues as of 2007-04-22

------------------------------------------------------

total: 5443     resolved: 3594

open: 1635

major 228, critical 90, BLOCKER 29

Resharper 4.0 Issues as of 2007-05-02

------------------------------------------------------

total: 5859 (+416 from 04/22)  resolved: 3925 (+331)

currently open: 1720 (+85)

237 Major, 99 Critical, 47 Blocker

So, let's check those figures out.  They've been hard at work and have knocked out 331 bugs.  But those little bug OPENERS (bastards) have been busier!!!  The open issues count has actually INCREASED by 85, and instead of 29 blockers, we now are delighted to note there are 47!!

That RTM will be out REAL SOON NOW

ok, I meant 2008 (ooops) and sorry 'bout all the blank lines (sometimes pasting in text isn't such a good idea)... anyway......

In case you did not read one of my past posts where I threatened to break up with R# 4.0 I have moved

Ephedrine. Ephedrine products. Ephedrine withdrawn. Addicted to ephedrine. Ephedrine side effects. Ephedrine hcl. Ephedrine faq. Ephedrine graphs. Baseball player dies from ephedrine.

yeah I get the Out of memory exceptions and tech support told me its my fault? wtf?

By the way people my bad If oyu get out of memory exceptions go here www.jetbrains.net/.../OutOfMemoryException+F

ix

A little late reaction:

Well I used Devexpress Refactor in the past and now I am a happy Resharper 4.1 user. The reason is they have a good shortcut key support (and you can easily get a hardcopy of the shortcut keys which you can stick below your monitor. Try this with Devexpress!) and somehow there refactoring advises feel more comfortable. I always got very annoyed with Devexpress popup's. Besides I always got the feeling Devexpress is slower.