Anyone here having no problems with Resharper?

I'm just wondering if I'm in the minority here by having frequent problems
with Resharper. I've always kept up to date with the latest releases but
I've never been able to get out of the woods. It doesn't seem that 30
minutes can go by without some issue popping up, be it an internal R# error
or incorrectly highlighted syntax. I know the JetBrains guys are working
really hard on this, but we are 12 months past the original planned release
of V2 and I still don't think it's solid. Maybe I'm being to hard, I dunno.


16 comments
Comment actions Permalink

Hello Rick,

the picture of (un)stability you've outlined definitely shouldn't be common,
and we are not experience such problems here.
Have you submitted the errors you got? Could you please post references to
some of the here?

Thanks.


Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


I'm just wondering if I'm in the minority here by having frequent
problems with Resharper. I've always kept up to date with the latest
releases but I've never been able to get out of the woods. It doesn't
seem that 30 minutes can go by without some issue popping up, be it an
internal R# error or incorrectly highlighted syntax. I know the
JetBrains guys are working really hard on this, but we are 12 months
past the original planned release of V2 and I still don't think it's
solid. Maybe I'm being to hard, I dunno.



0
Comment actions Permalink

The biggest problem I'm having is incorrectly analyzed in ASP.NET 2.0 web
site projects. By incorrectly analyzed code, I mean too many false errors
that compile without error. But I think I've found the cause, at least for
my machine, in news://news.jetbrains.com/da27a8e44eb4a8c910eb4e1c2d36@news.jetbrains.com.
I'm willing to accept this, to a certain extent, because it doesn't cause
VS.Net to crash or slow to the point where it becomes unusable and, lucky
for me, I don't work in ASP.NET 2.0 100% of the time.

Other than that, I consider myself pretty far out of the woods with Resharper
2.x.


0
Comment actions Permalink

On Mon, 29 Jan 2007 12:55:15 +0000 (UTC), flipdoubt
<flipdoubt@nospam.com> wrote:

>The biggest problem I'm having is incorrectly analyzed in ASP.NET 2.0 web
>site projects.

It's not a solution to your problem, but an aside: you owe it to
yourself to check out the new web application project type! It's
better in every way I can think of. I can't imagine what MS were
thinking of with the web site garbage.

- Casey

0
Comment actions Permalink

It's not a solution to your problem

Why do you say that? Have you suffered this problem and come across a different
solution? If so, what is it? If not, I think I'll wait for JetBrains to chime
in.

you owe it to yourself to check out the new web application project type!

I use the web application project on some of my projects, mostly those started
in ASP.NET 1.1. Coming from the WinForms world, the web application project's
single biggest advantage is that it works with how my mind thinks of projects
in VS.NET, but surely having a familiar development experience is not the
primary reason we're developing.

I struggled with the web site project model at first, but it does have its
advantages when it comes to deployment.

You have to way the advantages of each approach. I will admit, however, that
the complexity added by the new default project model for ASP.NET 2.0 make
the comparison an awefully close. So close that "why tinker with a good thing?"
has its merits.


0
Comment actions Permalink

"Rick" <rick@nospam.com> writes:

I know the JetBrains guys are working
really hard on this, but we are 12 months past the original planned release
of V2 and I still don't think it's solid. Maybe I'm being to hard, I dunno.


I'm using Resharper on a daily basis since 1.5 here and I followed
through the EAP of 2 ever since, have to say that the current 2.5.1
release is running very stable for me, so were the initial 2.5 release
and most "stable" EAP builds I used (I just kept looking for trouble
messages here in the newsgroup before trying it out myself).

Yet I have to confess that if I'm experiencing any troubles (with
Resharper or anything else), I just restart Visual Studio before being
angry for too long. I know, that's not really a problem solver, but its
the best I can do for my own productivity ;)

Best regards,
Martin

0
Comment actions Permalink

I don't have any real problems.

I'm not using ASP.NET though, which seems to be a sore spot, judging on
these forums.

---
Richard

"Rick" <rick@nospam.com> wrote in message
news:epk8ji$3nh$1@is.intellij.net...

I'm just wondering if I'm in the minority here by having frequent problems
with Resharper. I've always kept up to date with the latest releases but
I've never been able to get out of the woods. It doesn't seem that 30
minutes can go by without some issue popping up, be it an internal R#
error or incorrectly highlighted syntax. I know the JetBrains guys are
working really hard on this, but we are 12 months past the original
planned release of V2 and I still don't think it's solid. Maybe I'm being
to hard, I dunno.



0
Comment actions Permalink

On Mon, 29 Jan 2007 14:44:12 +0000 (UTC), flipdoubt
<flipdoubt@nospam.com> wrote:

>> It's not a solution to your problem
>Why do you say that? Have you suffered this problem and come across a different
>solution? If so, what is it? If not, I think I'll wait for JetBrains to chime
>in.

I was just trying to say that my suggestion to look at WAP was not a
solution to your current problem. But I'll leave you to nurse that
chip on your shoulder now.

- Casey

0
Comment actions Permalink

I was just trying to say that my suggestion to look at WAP was not a
solution to your current problem. But I'll leave you to nurse that
chip on your shoulder now.

Ooops. I misunderstood your "It's not a solution to your problem" to be my
hypothesis, not your suggestion.

My mistake. Sorry if I sounded testy. I guess I do have a chip on my shoulder.


0
Comment actions Permalink

Hi

We have lots and lots of problems using Resharper 2.5. Everyone on our team
has switch back to ReSharper 2.0.2 build 266.

The "OutOfMemberyError in lexing file" bug is totally blocking our
development, and it is so frustrating that nobody from the resharper team is
providing feedback on this bug.

The error is easily reproducable.

best regards
Torkil @ IBM

"Rick" <rick@nospam.com> wrote in message
news:epk8ji$3nh$1@is.intellij.net...

I'm just wondering if I'm in the minority here by having frequent problems
with Resharper. I've always kept up to date with the latest releases but
I've never been able to get out of the woods. It doesn't seem that 30
minutes can go by without some issue popping up, be it an internal R#
error or incorrectly highlighted syntax. I know the JetBrains guys are
working really hard on this, but we are 12 months past the original
planned release of V2 and I still don't think it's solid. Maybe I'm being
to hard, I dunno.



0
Comment actions Permalink

I also get OutOfMemory exception in 2.5.1 build 340 after opening and closing
solution a number of times. This is particular acute when I have to switch
between branch code and trunk code many times during the course of the day.

news.jetbrains.com wrote:

Hi

We have lots and lots of problems using Resharper 2.5. Everyone on our team
has switch back to ReSharper 2.0.2 build 266.

The "OutOfMemberyError in lexing file" bug is totally blocking our
development, and it is so frustrating that nobody from the resharper team is
providing feedback on this bug.

The error is easily reproducable.

best regards
Torkil @ IBM

"Rick" <rick@nospam.com> wrote in message
news:epk8ji$3nh$1@is.intellij.net...

>> I'm just wondering if I'm in the minority here by having frequent problems
>> with Resharper. I've always kept up to date with the latest releases but
>> I've never been able to get out of the woods. It doesn't seem that 30
>> minutes can go by without some issue popping up, be it an internal R#
>> error or incorrectly highlighted syntax. I know the JetBrains guys are
>> working really hard on this, but we are 12 months past the original
>> planned release of V2 and I still don't think it's solid. Maybe I'm being
>> to hard, I dunno.
>>


0
Comment actions Permalink

If you guys would allow crash dumps to be submitted anonymously you may get
better feedback. Why do you insist on a login anyway?

"Dmitry Shaporenkov" <dsha@jetbrains.com> wrote in message
news:c8a8945d0eaf8c911c339c74716@news.intellij.net...

Hello Rick,

>

the picture of (un)stability you've outlined definitely shouldn't be
common, and we are not experience such problems here.
Have you submitted the errors you got? Could you please post references to
some of the here?
Thanks.

>
>

Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>
>
>
>> I'm just wondering if I'm in the minority here by having frequent
>> problems with Resharper. I've always kept up to date with the latest
>> releases but I've never been able to get out of the woods. It doesn't
>> seem that 30 minutes can go by without some issue popping up, be it an
>> internal R# error or incorrectly highlighted syntax. I know the
>> JetBrains guys are working really hard on this, but we are 12 months
>> past the original planned release of V2 and I still don't think it's
>> solid. Maybe I'm being to hard, I dunno.
>>
>



0
Comment actions Permalink

Hello Rick,

We allow anonymous exceptions submitting in v2.5, but in realilty it doesn't
help much. The problem is that in many cases it is impossible to reproduce
a problem from the stack trace. Very few people give us comments when exception
occures, about what they were doing at the moment or right before the crash.
We understand this - people want to get rid of exception dialog as fast as
they can and continue their work. When exceptions are not anonymous we at
least can get back to the user and ask specific questions, so we can reproduce
the problem and fix it.

Sincerely,
Ilya Ryzhenkov

JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


R> If you guys would allow crash dumps to be submitted anonymously you
R> may get better feedback. Why do you insist on a login anyway?
R>
R> "Dmitry Shaporenkov" <dsha@jetbrains.com> wrote in message
R> news:c8a8945d0eaf8c911c339c74716@news.intellij.net...
R>
>> Hello Rick,
>>
>> the picture of (un)stability you've outlined definitely shouldn't be
>> common, and we are not experience such problems here.
>> Have you submitted the errors you got? Could you please post
>> references to
>> some of the here?
>> Thanks.
>> Dmitry Shaporenkov
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>>> I'm just wondering if I'm in the minority here by having frequent
>>> problems with Resharper. I've always kept up to date with the latest
>>> releases but I've never been able to get out of the woods. It
>>> doesn't seem that 30 minutes can go by without some issue popping
>>> up, be it an internal R# error or incorrectly highlighted syntax. I
>>> know the JetBrains guys are working really hard on this, but we are
>>> 12 months past the original planned release of V2 and I still don't
>>> think it's solid. Maybe I'm being to hard, I dunno.
>>>


0
Comment actions Permalink

Hello Torkil,

n> The error is easily reproducable.
We can't reproduce the problem here in labs for the whole lifetime of the
problem. I mean reproduce it reliably, so we can run with debugger or memory
profiler and spot the source of the OutOfMemoryException, which is plaguing
us for years. Every time people tell us that the problem can be reproduced
easily, and if we manage to get the project sources from the customer, we
can't reproduce it here. May be it is ReSharper conflicting with some other
component installed, which we was not able to identify. Or may be it is specific
memory conditions, which are normal for the customer but not the case for
our dev team. We just don't know. It's a kind of magic... Stack traces are
of no help, because there is nothing criminal in there, something bad happens
before the problem occures and then memory begins to leak, which leads to
OOM exception eventually, depending on RAM available.

It could help, if you could identify what you do from the very start of VS
session which reliably leads to OOM exception. Then, we may need your configuration
files, and probably solution sources, and list of installed .NET components,
addins, system components which interact with .NET like IIS or whatever.
We will try our best to nail down the problem, if you could help to reproduce
it. If you need an NDA to send information, we can manage it.

Sincerely,
Ilya Ryzhenkov

JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


n> Hi
n>
n> We have lots and lots of problems using Resharper 2.5. Everyone on
n> our team has switch back to ReSharper 2.0.2 build 266.
n>
n> The "OutOfMemberyError in lexing file" bug is totally blocking our
n> development, and it is so frustrating that nobody from the resharper
n> team is providing feedback on this bug.
n>
n> The error is easily reproducable.
n>
n> best regards
n> Torkil @ IBM
n> "Rick" <rick@nospam.com> wrote in message
n> news:epk8ji$3nh$1@is.intellij.net...
n>
>> I'm just wondering if I'm in the minority here by having frequent
>> problems with Resharper. I've always kept up to date with the latest
>> releases but I've never been able to get out of the woods. It doesn't
>> seem that 30 minutes can go by without some issue popping up, be it
>> an internal R# error or incorrectly highlighted syntax. I know the
>> JetBrains guys are working really hard on this, but we are 12 months
>> past the original planned release of V2 and I still don't think it's
>> solid. Maybe I'm being to hard, I dunno.
>>


0
Comment actions Permalink

Hello,

I also get OutOfMemory exception in 2.5.1 build 340 after opening and
closing solution a number of times. This is particular acute when I
have to switch between branch code and trunk code many times during
the course of the day.


Generally, it's better to restart the whole Visual Studio in such a case
— because it takes the same time, but clears out all the leftovers from the
previous solution.

It doesn't mean we won't strive for fixing this exception, of course :) But
VS itself is prone to memory leaks, too, aside from ReSharper.


Serge Baltic
Omea & R# Developer
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”


0
Comment actions Permalink

Sounds reasonable. Thanks.

"Ilya Ryzhenkov" <orangy@netix.ru> wrote in message
news:9f6b3e291321218c912890c7d0677@news.intellij.net...

Hello Rick,

>

We allow anonymous exceptions submitting in v2.5, but in realilty it
doesn't help much. The problem is that in many cases it is impossible to
reproduce a problem from the stack trace. Very few people give us comments
when exception occures, about what they were doing at the moment or right
before the crash. We understand this - people want to get rid of exception
dialog as fast as they can and continue their work. When exceptions are
not anonymous we at least can get back to the user and ask specific
questions, so we can reproduce the problem and fix it.

>

Sincerely,
Ilya Ryzhenkov

>

JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>
>

R> If you guys would allow crash dumps to be submitted anonymously you
R> may get better feedback. Why do you insist on a login anyway?
R> R> "Dmitry Shaporenkov" <dsha@jetbrains.com> wrote in message
R> news:c8a8945d0eaf8c911c339c74716@news.intellij.net...
R>

>>> Hello Rick,
>>>
>>> the picture of (un)stability you've outlined definitely shouldn't be
>>> common, and we are not experience such problems here.
>>> Have you submitted the errors you got? Could you please post
>>> references to
>>> some of the here?
>>> Thanks.
>>> Dmitry Shaporenkov
>>> JetBrains, Inc
>>> http://www.jetbrains.com
>>> "Develop with pleasure!"
>>>> I'm just wondering if I'm in the minority here by having frequent
>>>> problems with Resharper. I've always kept up to date with the latest
>>>> releases but I've never been able to get out of the woods. It
>>>> doesn't seem that 30 minutes can go by without some issue popping
>>>> up, be it an internal R# error or incorrectly highlighted syntax. I
>>>> know the JetBrains guys are working really hard on this, but we are
>>>> 12 months past the original planned release of V2 and I still don't
>>>> think it's solid. Maybe I'm being to hard, I dunno.
>>>>
>



0
Comment actions Permalink

You could allow users to post exceptions anonymously, but invite them to
optionally leave their email address in case you need to contact them for
more information and, if possible, they want to receive updates regarding
the bug.

Dag

"Rick" <rick@nospam.com> wrote in message
news:eppe5m$10c$1@is.intellij.net...

Sounds reasonable. Thanks.

>

"Ilya Ryzhenkov" <orangy@netix.ru> wrote in message
news:9f6b3e291321218c912890c7d0677@news.intellij.net...

>> Hello Rick,
>>
>> We allow anonymous exceptions submitting in v2.5, but in realilty it
>> doesn't help much. The problem is that in many cases it is impossible to
>> reproduce a problem from the stack trace. Very few people give us
>> comments when exception occures, about what they were doing at the moment
>> or right before the crash. We understand this - people want to get rid of
>> exception dialog as fast as they can and continue their work. When
>> exceptions are not anonymous we at least can get back to the user and ask
>> specific questions, so we can reproduce the problem and fix it.
>>
>> Sincerely,
>> Ilya Ryzhenkov
>>
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"


0

Please sign in to leave a comment.