ReSharper EAP Reliability
I've been using the ReSharper 2 EAP for VS2005 and VS2003 since it was
available. I'm a big fan of ReSharper and was sorely missing it for the
early betas of VS2005 so please bear this in mind.
Today I've uninstalled the ReSharper 2.0 EAP on both VS2003 and VS2005.
I was using the latest EAP build 210. In the last few builds it seems to
been getting more and more buggy, to the extent now that it's becoming
unusable.
Most of the features don't work:
Many refactorings tend to hang VS, with the processor pegged at near
100% - not good as this can lose work. So I stopped using refactorings
altogether.
Intellisense just keeps saying no suggestions and doesn't pop up on
"." any more - I have to use the Ctrl-Space and its variants. Since it
doesn't give any info, though, I switched back to VS intellisense.
Exception tracking dialog pops up very frequently and tends to get
into a loop with new exceptions, even if the ignore option is ticked.
This requires killing VS, again losing work.
I have to delete the ReSharper cache before loading a solution or I
get exceptions immediately in many cases.
At the same time each new EAP release seems to add additional
refactoring and other new features.
My plea is: please focus on improving the EAP stability before adding
any new features. I'll try each new EAP build but if stability doesn't
improve, I'll have to uninstall immediately.
I read the recent posting by someone making similar comments and he was
flamed. I suppose I'll get flamed too, but I do sincerely want to help
to make ReSharper 2.0 a great product. The only way to do this is to use
it for real work. You can't dogfood by just having a quick taste of a
new build - you have to use it for real work. So please take these
comments as positive suggestions on the current development focus.
Cheers,
MikeS.
Please sign in to leave a comment.
>I have CHOSEN to install EAP build # 210 and nobody OBLIGATED me to install
>one of the EAP builds so with al do respect if you don't like the EAP
>builds uninstall them and go back to version # 1.5.1 but please please stop
>whining about it already.
I totally disagree with this...
I used 1.5 and it saved me a lot of work. Now I have upgraded to VS2005
(which was obligatory for me as we need features from the Framework 2.0) and
I am missing lots of the functionality provided by R#, reducing my
productivity.
But now there is no alternative then the EAP (so I AM OBLIGATED). Basically,
I have purchased a product which has become unuseful until ???.
You could argue that I should be glad that I can upgrade for free to 2.0
(and I am :) ), but IMHO maybe it would have made more sense if JetBrains
had released a version for VS2005 that is free for 1.5 users but has no
additional functionality and to introduce another version with all the new
(undoubtly very valuable) features, that could be upgraded to for a fee.
Then the focus could have been on bug fixing and 1.5 users could have
continued with the same productivity on VS2005.
It is not so hard to wait for the new features, it's very hard to miss the
original features.
Patrick
Support of C# 2.0 constructs (such as generics) is itself a big feature.
And not the one which is easy to implement. It took (and is taking now) considerable
amount of efforts for our development team to support them. We've added also
lot of other functionality because we want to bring more features to our
users. But we had no choice of doing these 2 activities separately.
Valentin Kipiatkov
Chief Scientist, Vice President of Product Development
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
>> I have CHOSEN to install EAP build # 210 and nobody OBLIGATED me to
>> install one of the EAP builds so with al do respect if you don't like
>> the EAP builds uninstall them and go back to version # 1.5.1 but
>> please please stop whining about it already.
>>
Hello Patrick,
you have purchased a product called ReSharper 1.x for Visual Studio 2003.
Nobody
here promised that it will work for Visual Studio 2005 or there will be a
version of 1.x
for Visual Studio 2005 - in fact, we never had
such plans. Nor it is possible to do that now. Instead, IMO, we should focus
on stability and performance
of 2.0 EAP builds, which we're trying to do.
Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
Hello Dmitry
When I buy a software product, I expect it to work on a next platform OR
that there will be an upgraded version for that new platform, regardless if
that will be a free or paid upgrade.
I did not mean with my remark you quoted that I expected a free upgrade to
VS2005 when I bought R#. What I did expect was continuity. The fact that I
can not use R# for an indefinite time breaks this continuity and costs me
more money than a paid upgrade would have cost with only the 1.5 features
but compatible with VS2005.
R# is an invaluable part of my toolset for over a year now. The fact that
the absence of R# causes a significant productivity loss is a compliment for
you and your product, but is a frustrating daily reality for me.
>
There is no doubt on my mind you are.
Regards,
Patrick
There will be a new version. We are working on it and the release is near
(planned for the Febrary). We could not deliver it earlier. It's difficult
or sometimes impossible to develop an application for a platform/environment
which itself is not yet stable. VS2005 RTM's were very unstable (with lot
of functionality broken) until the summer. Anyway we are soory for the inconvenience
caused by absence of stable ReSharper for VS2005 in these few months until
2.0 release.
Valentin Kipiatkov
Chief Scientist, Vice President of Product Development
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
>> you have purchased a product called ReSharper 1.x for Visual Studio
>> 2003.
>> Nobody
>> here promised that it will work for Visual Studio 2005 or there will
>> be a
>> version of 1.x for Visual Studio 2005
>> Instead, IMO, we should focus on stability and performance of 2.0 EAP
>> builds, which we're trying to do.
>>