Is the EAP for ReSharper 6.x is a done thing ? Follow

Seriously, I'd like to know whether you are planning to fix the current bugs of ReSharper 6.x or push it all to the next version ?

Hello Eyal
     Sorry for delayed response! I'm afraid at the moment we cannot tell exactly if there will be more bugfix updates for ReSharper 6.x or not. I'll write back as soon as I have more information for you. Thank you!

Andrey Serebryansky

Senior Support Engineer

JetBrains, Inc

http://www.jetbrains.com

"Develop with pleasure!"

So to put it otherwise, you're saying that major bugs won't be fixed and I'm basically forced to buy Visual Studio 2012 and ReSharper 7.0 ?

I suppose the next question is do we start the procession again, performance issues in 6
were never fully resolved and if I read the response correctly (between the lines) they never will be, now we will have a whole new set of bugs to work through

Sorry if I sound synical, I eventually gave up on V 6 and Jet Brains kindly refunded my upgrdae cost from 5-> 6

I for one will think very hard before upgrading to 7

The competitors must be planning a field day

Mike

Indeed I fully agree with you Mike.

I've been  using JetBrains products for years throughout my career as a developer  and I never been so disappointed, I like most of your products and I'm  using them daily!

I don't have problems with bugs, I do have problems with them when they don't get fixed and by your philosophy I need to wait another version (maybe few) for the bugs to be fixed.

I don't want to give up on your products but eventually and I really feel the frustration of Mike here, I'll do the same and look elsewhere.

Live Templates is something I use daily! yet it's broken, it's useless! and I can do nothing about it.

I don't want a refund but no way I'm going to buy R#7 for the full price  when the amount of frustration I went through for a tool that suppose  to make me more productive even less so.

I own CodeRush but I like R# better, please, don't let me go back to something that I prefer a lot less, right now I don't have a choice.

Hello Eyal
     I completely understand your disappointment, we will discuss if the problem with Live Templates can be fixed in ReSharper 6.x. Thank you!

Andrey Serebryansky

Senior Support Engineer

JetBrains, Inc

http://www.jetbrains.com

"Develop with pleasure!"

Well, I'd definitely reconsider if the Live Templates are going to be fixed because I'm using them A LOT! and right now I can't because this template is just one of many I use and it's basically broken; not to mention that I already reported about this probelm once during the EAP of R#6.

How about other critical bugs? Is it just a case of whoever shouts loudest gets their bugs fixed?

For example: RSRP-288359

• In 5.x and 6.0, you couldn't set the C# language level for a web-site project without manually editing the ".ReSharper" file.
• In 6.1 and 6.1.1, the property has been added, but now NONE of the settings are saved, and there is NO workaround.
• The bug hasn't been updated since February, and currently has a "fix version" of "7.0".

How about fixing intellisense to account for the fact that C# is case-sensitive?
(Fix version "Mirabile Futurum", which is Latin for "the consequence would be wonderful", and presumably means it's never going to get fixed?)

How about problems with optional "out" parameters which have been around since at least v5?
(Fix version "7.0" - hey, only two major versions since it was reported!)

And we're supposed to believe that you haven't given up on 6.x as a lost cause?

I haven't given up on R# yet because I actually love this product and I respect JetBrains for their existing products that I also consume, I've been writing macros and custom templates to enhance my productivity so when this feature fails things that took 1sec to accomplish can become fairly tedious.

I just payed for something that is not fully functional, Live Templates  is important feature that I used on daily basis and I expect this to  work properly, that's all.

It's not my place to prioritise or making the schedule for JetBrains but it's definitely my place to make sure I get what I pay for and get it fixed if possible; otherwise, I'll just fall back to older versions or different kinds of products.

Sorry, the "you" in the last sentence meant JetBrains. Given the number of fairly critical bugs which have been postponed to v7, I suspect they've given up on v6.

Oh!.. haha ;)

I serisouly don't understand why the most important thing is to have a new version rather than fixing existing bugs and I should say quite major ones in the current version.

I suppose it really boils down to the question , is there actually versions of a product are are we onboard for an ever "improving" product

The version of the day is the one we use. Obvioulsy as .NET technology moves on , the tools we use must obviously move on to keep pace, the decompile tools like Reflector, Dot Peek  et al. they are almost duty bound to keep up  with new framwork changes.

What that means in terms of Updates , versions etc is the real question.

Maybe its how Jet Brains run their licenses , I have licenses for products that just keep evolving . A good non competitve example is SQL Prompt . The license is an up front payment and an annual top up typically 30% of starter cost. For that any changes to the product are yours to upgrade . So in essence there is , for a license holder, only one version of SQL Prompt , the CURRENT one , and all efforts , bug fixes etc are applied to that version to keep the users up to date.

There are many examples of this style of licensing.

Jet Brains on the other hand opt for a specific version and an upgrade cost to move from 5 to 6 , 6 to 7 etc. By discretely separating out versions , it is likely that the NEW version gets all the attnetion , as quite rightly (Commercially)  that is where the next injection of money is to come from.

Maybe maintaining one version and adding extra features to it is a better option as the OLD version never really gets left behind. As far as tools I use and indeed the product I develop and maintain , this seems to be the pattern

Food for thought ....

Mike

Hello Eyal and Richard,
     ReSharper 6.0 was released by the end of June 2011 and the latest ReSharper 6.1.1 was released on 16th February 2012, which means that we've been providing bugfix updates to v6 for almost 8 months.  We did our best to fix the most critical and outstanding bugs as well as provided some new features. If you've found really critical bugs that prevent you from using ReSharper, please let me know and we'll see what we can do.

Andrey Serebryansky

Senior Support Engineer

JetBrains, Inc

http://www.jetbrains.com

"Develop with pleasure!"

You can't justify yourself by saying that you have been fixing bugs the past 8 months! some major features are still broken and really I'm pissed because I actually care!

We don't want new features! we want the current features to work correctly! as you advertised them to be during the lifecycle of R#5 and R#6.

Before I'm even thinking about R#7.0 I want the current product that I bought to work as expcted, I want to upgrade on my own terms not because R#7.0 is going to fix major bugs in R#6.0!

Either you will do a full refund, fix the bugs or let us upgrade to R#7.0 for free or don't do that and I'll give up on any of your products including my company, your choice because currently I'm not satisfied.

The easiest option is to refund my money which in all honesty I don't really want, I want to use the product and for that product to be usable.

Sorry for all the exclamation marks.

I would say that

It seems like it was a bad idea to make a major change to the settings engine in a minor update, as it seems to have caused more problems than it solved.