Had to revert back to 1.5

Resharper 2.0 kept throwing a null reference exception when trying to load
one of my large solutions, always at the same spot. Two exception reports
were submitted that should be identical.

I eagerly look forward to the next drop.


3 comments
Comment actions Permalink

You name is well-known among us as a person with a lot of good suggestions
and valuable feedbacks :)

I hope you will try the next build

--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Paul Bradshaw" <pbradshaw@advsol.com> wrote in message
news:dbkr0n$gr$1@is.intellij.net...

Resharper 2.0 kept throwing a null reference exception when trying to load
one of my large solutions, always at the same spot. Two exception reports
were submitted that should be identical.

>

I eagerly look forward to the next drop.

>



0
Comment actions Permalink

Oh, I will, rest assured :)


"Eugene Pasynkov (JetBrains)" <Eugene.Pasynkov@jetbrains.com> wrote in
message news:dbl206$q7a$1@is.intellij.net...

You name is well-known among us as a person with a lot of good suggestions
and valuable feedbacks :)

>

I hope you will try the next build

>

--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Paul Bradshaw" <pbradshaw@advsol.com> wrote in message
news:dbkr0n$gr$1@is.intellij.net...

>> Resharper 2.0 kept throwing a null reference exception when trying to
>> load one of my large solutions, always at the same spot. Two exception
>> reports were submitted that should be identical.
>>
>> I eagerly look forward to the next drop.
>>
>>
>



0
Comment actions Permalink

After working with 202 for a while, I had to revert back to 1.5 again. I
eagerly look forward to the next drop.

Reasons:
1) Still way too slow on start up (and I generally have to restart several
times a day)
2) Too unstable (many exceptions, and generally the result is that
identifiers all show up as unresolved and I have to restart... see 1)
3) Problems with finding usages renders refactoring unusable. I think this
is related to the 'references' issue that was fixed in 1.5, but existed
prior to 1.5, where the same type and method wasn't recognized if it was
referenced from the same DLL but in a different location... but that's just
a guess.

"Eugene Pasynkov (JetBrains)" <Eugene.Pasynkov@jetbrains.com> wrote in
message news:dbl206$q7a$1@is.intellij.net...

You name is well-known among us as a person with a lot of good suggestions
and valuable feedbacks :)

>

I hope you will try the next build

>

--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Paul Bradshaw" <pbradshaw@advsol.com> wrote in message
news:dbkr0n$gr$1@is.intellij.net...

>> Resharper 2.0 kept throwing a null reference exception when trying to
>> load one of my large solutions, always at the same spot. Two exception
>> reports were submitted that should be identical.
>>
>> I eagerly look forward to the next drop.
>>
>>
>



0

Please sign in to leave a comment.