Had to uninstall build 230

It was horrible. It could not understand any symbols... everything was red.
It insisted everything was an ambiguous reference or was multiply defined
("are you missing a 'partial' declaration?) when that was NOT the case.
Could not even navigate.

VERY VERY slow.

Restarting had no effect.

Completely unusable for me. I'm backing off to the previous build now to
see if things are fixed up using that... I have no idea what happened.
I've had very good experiences with the recent builds, but this one didn't
last more than two minutes (once the ten minutes of loading finished...
yeesh!) on my system.



21 comments
Comment actions Permalink

I have had a similar experience. R# Intellisense is horribly broken for me. Will appear for first couple of characters and then just dissapears. Also throwing many, many exceptions (all which have been submitted to tracker). Back to 229

0
Comment actions Permalink

Same here. And the MS intellisense is broken too, if you choose to use its features instead of R#.

0
Comment actions Permalink

Yeah, I'm back with 219 which has it own set of problems but is more usable.

0
Comment actions Permalink

I rolled back to 229, and I'm fine.

230 was completely unusable for me.


"alastair" <no_reply@jetbrains.com> wrote in message
news:23021862.1143661582762.JavaMail.itn@is.intellij.net...

Yeah, I'm back with 219 which has it own set of problems but is more
usable.



0
Comment actions Permalink

230 works great here.
Do you guys uninstall ReSharper before installing a new version? I always do.

0
Comment actions Permalink

Yes, I also delete the _Resharper folders. How large/complex is your solution?

0
Comment actions Permalink

Usually not. Perhaps I'll give that a try.

0
Comment actions Permalink

try 231, it's out now.

0
Comment actions Permalink

~70 projects. All C#.

0
Comment actions Permalink

231 is much better.

0
Comment actions Permalink

Build 231 returns to being useable. Whew!


"alastair" <no_reply@jetbrains.com> wrote in message
news:4033282.1143665883446.JavaMail.itn@is.intellij.net...

try 231, it's out now.



0
Comment actions Permalink

I take it back... I spoke too soon. I didn't wait long enough for all the
assemblies to be parsed ... everything is underlined in red again. It
doesn't recognize anything. I even deleted the caches and restarted. That
fixed some things, but not everything.

Lots of "Ambiguous references" that aren't ambiguous at all.

I'm might have to have to roll back to build 229 again. 331 is better than
330 I think, but still... I'll try and continue using for a little longer
and see what happens.


"alastair" <no_reply@jetbrains.com> wrote in message
news:4033282.1143665883446.JavaMail.itn@is.intellij.net...

try 231, it's out now.



0
Comment actions Permalink

Hello Paul,

could you please elaborate on the problem - what types are underlined in
red and where (i.e. in what projects or assemblies) are they declared? Thanks.


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

I take it back... I spoke too soon. I didn't wait long enough for all
the assemblies to be parsed ... everything is underlined in red again.
It doesn't recognize anything. I even deleted the caches and
restarted. That fixed some things, but not everything.

Lots of "Ambiguous references" that aren't ambiguous at all.

I'm might have to have to roll back to build 229 again. 331 is
better than 330 I think, but still... I'll try and continue using for
a little longer and see what happens.

"alastair" <no_reply@jetbrains.com> wrote in message
news:4033282.1143665883446.JavaMail.itn@is.intellij.net...

>> try 231, it's out now.
>>


0
Comment actions Permalink

I also am seeing more red than I ever.

I have projects that have a reference to a dll "RoData.dll" with some
classes I use. the code compiles and runs fine but any where in the
code that I reference a class from the above mentioned dll is says:

"Module 'ROData' should be referenced"

It is referenced. So, I don't know what the confusion is here.

Could it possibly be that the case is different? The dll is named
RoData.dll but the namespace is Mpi.Argis.Vm.Sms.ROData.

Just a stab in the dark.

Steve Messer
Mobile Productivity, Inc



On Thu, 30 Mar 2006 04:45:31 +0000 (UTC), Dmitry Shaporenkov
(JetBrains) <dsha@jetbrains.com> wrote:

>Hello Paul,
>
>could you please elaborate on the problem - what types are underlined in
>red and where (i.e. in what projects or assemblies) are they declared? Thanks.
>
>
>Regards,
>Dmitry Shaporenkov
>JetBrains, Inc
>http://www.jetbrains.com
>"Develop with pleasure!"
>
>> I take it back... I spoke too soon. I didn't wait long enough for all
>> the assemblies to be parsed ... everything is underlined in red again.
>> It doesn't recognize anything. I even deleted the caches and
>> restarted. That fixed some things, but not everything.
>>
>> Lots of "Ambiguous references" that aren't ambiguous at all.
>>
>> I'm might have to have to roll back to build 229 again. 331 is
>> better than 330 I think, but still... I'll try and continue using for
>> a little longer and see what happens.
>>
>> "alastair" <no_reply@jetbrains.com> wrote in message
>> news:4033282.1143665883446.JavaMail.itn@is.intellij.net...
>>
>>> try 231, it's out now.
>>>
>

0
Comment actions Permalink

I have a one project in a solution of a dozen projects. This project is a
"unit test project" (simple library project with all our unit tests in it).

In this project, there's a static utility class defined "Foo.Bar.Baz". It
has a bunch of static methods for doing things. Every time a static method
is referenced for "Baz.MyMethod()", the "Baz" is underlined and it is
claimed to be ambigious. If you right click on it and try to go to
definition, you see two entries that are identical. If you select one,
you go to the top of the file as you should (the definition for this class).
If you select the other one, you end up in the Class Browser for some
reason.

All the references are fine, it compiles fine, and previous versions of
ReSharper didn't seem to have this problem.

My best guess at what's going on is the DLL/Reference issue... but even that
doesn't explain it for me. Most of our projects are copied into a single
'bin' directory because they all need to dynamically reference each other at
run-time. Unit Test files, however, go into a separate directory. My only
thinking is that Resharper is trying to "unify" the project/dll references
with these last two versions, and isn't quite doing it correctly in this
case... somehow seeing the same class defined in two places and not
realizing they're the SAME class.

But it's not obvious to me exactly where the problem is, and why some
classes are showing this, and others aren't.


"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d913dcfa8c821ed6fbe4668@news.intellij.net...

Hello Paul,

>

could you please elaborate on the problem - what types are underlined in
red and where (i.e. in what projects or assemblies) are they declared?
Thanks.

>
>

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

>
>> I take it back... I spoke too soon. I didn't wait long enough for all
>> the assemblies to be parsed ... everything is underlined in red again.
>> It doesn't recognize anything. I even deleted the caches and
>> restarted. That fixed some things, but not everything.
>>
>> Lots of "Ambiguous references" that aren't ambiguous at all.
>>
>> I'm might have to have to roll back to build 229 again. 331 is
>> better than 330 I think, but still... I'll try and continue using for
>> a little longer and see what happens.
>>
>> "alastair" <no_reply@jetbrains.com> wrote in message
>> news:4033282.1143665883446.JavaMail.itn@is.intellij.net...
>>
>>> try 231, it's out now.
>>>
>



0
Comment actions Permalink

Another error... for some reason, it's showing a using statement as
"redundant", and offering to remove it (and an optimize usings will indeed
get rid of it), but the project will not compile without it. This too is
because of an "ambibuous reference" to another class in the same project.
Apparently, when it sees these ambiguous references, it's counting it as no
reference at all... and doesn't think the using statement is necessary.




"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d913dcfa8c821ed6fbe4668@news.intellij.net...

Hello Paul,

>

could you please elaborate on the problem - what types are underlined in
red and where (i.e. in what projects or assemblies) are they declared?
Thanks.

>
>

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

>
>> I take it back... I spoke too soon. I didn't wait long enough for all
>> the assemblies to be parsed ... everything is underlined in red again.
>> It doesn't recognize anything. I even deleted the caches and
>> restarted. That fixed some things, but not everything.
>>
>> Lots of "Ambiguous references" that aren't ambiguous at all.
>>
>> I'm might have to have to roll back to build 229 again. 331 is
>> better than 330 I think, but still... I'll try and continue using for
>> a little longer and see what happens.
>>
>> "alastair" <no_reply@jetbrains.com> wrote in message
>> news:4033282.1143665883446.JavaMail.itn@is.intellij.net...
>>
>>> try 231, it's out now.
>>>
>



0
Comment actions Permalink

That was it for me.


Just to give a little background. I had a project named RoData but due
to a company naming policy and FxCop I was asked to rename my project
to ROData but just renaming the project is not enough for resharper
anyways.

Once I have anything using the same case ie ROData and not mixed
RoData and ROData all my red goes away.

So I gues it's good that resharper is case sensitive but, should it
be?

I don't know one way or the other. My problem came from renaming
things after the initial creation of the project.

Steve




On Thu, 30 Mar 2006 04:45:31 +0000 (UTC), Dmitry Shaporenkov
(JetBrains) <dsha@jetbrains.com> wrote:

>Hello Paul,
>
>could you please elaborate on the problem - what types are underlined in
>red and where (i.e. in what projects or assemblies) are they declared? Thanks.
>
>
>Regards,
>Dmitry Shaporenkov
>JetBrains, Inc
>http://www.jetbrains.com
>"Develop with pleasure!"
>
>> I take it back... I spoke too soon. I didn't wait long enough for all
>> the assemblies to be parsed ... everything is underlined in red again.
>> It doesn't recognize anything. I even deleted the caches and
>> restarted. That fixed some things, but not everything.
>>
>> Lots of "Ambiguous references" that aren't ambiguous at all.
>>
>> I'm might have to have to roll back to build 229 again. 331 is
>> better than 330 I think, but still... I'll try and continue using for
>> a little longer and see what happens.
>>
>> "alastair" <no_reply@jetbrains.com> wrote in message
>> news:4033282.1143665883446.JavaMail.itn@is.intellij.net...
>>
>>> try 231, it's out now.
>>>
>

0
Comment actions Permalink

Hello Paul,

I think that there is a known problem in builds 230/231 that causes
ReSharper to confuse property names with type names. In such a case you
can get spurious 'Ambiguous reference' errors.


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

Another error... for some reason, it's showing a using statement as
"redundant", and offering to remove it (and an optimize usings will
indeed get rid of it), but the project will not compile without it.
This too is because of an "ambibuous reference" to another class in
the same project. Apparently, when it sees these ambiguous references,
it's counting it as no reference at all... and doesn't think the using
statement is necessary.

"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d913dcfa8c821ed6fbe4668@news.intellij.net...

>> Hello Paul,
>>
>> could you please elaborate on the problem - what types are underlined
>> in red and where (i.e. in what projects or assemblies) are they
>> declared? Thanks.
>>
>> Regards,
>> Dmitry Shaporenkov
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>>> I take it back... I spoke too soon. I didn't wait long enough for
>>> all the assemblies to be parsed ... everything is underlined in red
>>> again. It doesn't recognize anything. I even deleted the caches and
>>> restarted. That fixed some things, but not everything.
>>>
>>> Lots of "Ambiguous references" that aren't ambiguous at all.
>>>
>>> I'm might have to have to roll back to build 229 again. 331 is
>>> better than 330 I think, but still... I'll try and continue using
>>> for
>>> a little longer and see what happens.
>>> "alastair" <no_reply@jetbrains.com> wrote in message
>>> news:4033282.1143665883446.JavaMail.itn@is.intellij.net...
>>>
>>>> try 231, it's out now.
>>>>


0
Comment actions Permalink

I'll be sure to check to see if build 232 fixes this problem then (assuming
this issue you describe is indeed fixed in build 232).

"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d913e8838c82253ea04df8c@news.intellij.net...

Hello Paul,

>

I think that there is a known problem in builds 230/231 that causes
ReSharper to confuse property names with type names. In such a case you
can get spurious 'Ambiguous reference' errors.

>
>

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

>
>> Another error... for some reason, it's showing a using statement as
>> "redundant", and offering to remove it (and an optimize usings will
>> indeed get rid of it), but the project will not compile without it.
>> This too is because of an "ambibuous reference" to another class in
>> the same project. Apparently, when it sees these ambiguous references,
>> it's counting it as no reference at all... and doesn't think the using
>> statement is necessary.
>>
>> "Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
>> news:c8a894d913dcfa8c821ed6fbe4668@news.intellij.net...
>>
>>> Hello Paul,
>>>
>>> could you please elaborate on the problem - what types are underlined
>>> in red and where (i.e. in what projects or assemblies) are they
>>> declared? Thanks.
>>>
>>> Regards,
>>> Dmitry Shaporenkov
>>> JetBrains, Inc
>>> http://www.jetbrains.com
>>> "Develop with pleasure!"
>>>> I take it back... I spoke too soon. I didn't wait long enough for
>>>> all the assemblies to be parsed ... everything is underlined in red
>>>> again. It doesn't recognize anything. I even deleted the caches and
>>>> restarted. That fixed some things, but not everything.
>>>>
>>>> Lots of "Ambiguous references" that aren't ambiguous at all.
>>>>
>>>> I'm might have to have to roll back to build 229 again. 331 is
>>>> better than 330 I think, but still... I'll try and continue using
>>>> for
>>>> a little longer and see what happens.
>>>> "alastair" <no_reply@jetbrains.com> wrote in message
>>>> news:4033282.1143665883446.JavaMail.itn@is.intellij.net...
>>>>
>>>>> try 231, it's out now.
>>>>>
>



0
Comment actions Permalink

Hello Paul,

I'm not sure that this issue has been already fixed in 232, but, if it hasn't,
it will definitely be fixed ASAP.


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

I'll be sure to check to see if build 232 fixes this problem then
(assuming this issue you describe is indeed fixed in build 232).

"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d913e8838c82253ea04df8c@news.intellij.net...

>> Hello Paul,
>>
>> I think that there is a known problem in builds 230/231 that causes
>> ReSharper to confuse property names with type names. In such a case
>> you can get spurious 'Ambiguous reference' errors.
>>
>> Regards,
>> Dmitry Shaporenkov
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>>> Another error... for some reason, it's showing a using statement as
>>> "redundant", and offering to remove it (and an optimize usings will
>>> indeed get rid of it), but the project will not compile without it.
>>> This too is because of an "ambibuous reference" to another class in
>>> the same project. Apparently, when it sees these ambiguous
>>> references, it's counting it as no reference at all... and doesn't
>>> think the using statement is necessary.
>>>
>>> "Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in
>>> message news:c8a894d913dcfa8c821ed6fbe4668@news.intellij.net...
>>>
>>>> Hello Paul,
>>>>
>>>> could you please elaborate on the problem - what types are
>>>> underlined in red and where (i.e. in what projects or assemblies)
>>>> are they declared? Thanks.
>>>>
>>>> Regards,
>>>> Dmitry Shaporenkov
>>>> JetBrains, Inc
>>>> http://www.jetbrains.com
>>>> "Develop with pleasure!"
>>>>> I take it back... I spoke too soon. I didn't wait long enough for
>>>>> all the assemblies to be parsed ... everything is underlined in
>>>>> red again. It doesn't recognize anything. I even deleted the
>>>>> caches and restarted. That fixed some things, but not everything.
>>>>>
>>>>> Lots of "Ambiguous references" that aren't ambiguous at all.
>>>>>
>>>>> I'm might have to have to roll back to build 229 again. 331 is
>>>>> better than 330 I think, but still... I'll try and continue using
>>>>> for
>>>>> a little longer and see what happens.
>>>>> "alastair" <no_reply@jetbrains.com> wrote in message
>>>>> news:4033282.1143665883446.JavaMail.itn@is.intellij.net...
>>>>>> try 231, it's out now.
>>>>>>


0
Comment actions Permalink

Build 232 does seem to fix this problem. Thanks!

"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d913f3788c822b32939b29c@news.intellij.net...

Hello Paul,

>

I'm not sure that this issue has been already fixed in 232, but, if it
hasn't, it will definitely be fixed ASAP.

>
>

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

>
>> I'll be sure to check to see if build 232 fixes this problem then
>> (assuming this issue you describe is indeed fixed in build 232).
>>
>> "Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
>> news:c8a894d913e8838c82253ea04df8c@news.intellij.net...
>>
>>> Hello Paul,
>>>
>>> I think that there is a known problem in builds 230/231 that causes
>>> ReSharper to confuse property names with type names. In such a case
>>> you can get spurious 'Ambiguous reference' errors.
>>>
>>> Regards,
>>> Dmitry Shaporenkov
>>> JetBrains, Inc
>>> http://www.jetbrains.com
>>> "Develop with pleasure!"
>>>> Another error... for some reason, it's showing a using statement as
>>>> "redundant", and offering to remove it (and an optimize usings will
>>>> indeed get rid of it), but the project will not compile without it.
>>>> This too is because of an "ambibuous reference" to another class in
>>>> the same project. Apparently, when it sees these ambiguous
>>>> references, it's counting it as no reference at all... and doesn't
>>>> think the using statement is necessary.
>>>>
>>>> "Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in
>>>> message news:c8a894d913dcfa8c821ed6fbe4668@news.intellij.net...
>>>>
>>>>> Hello Paul,
>>>>>
>>>>> could you please elaborate on the problem - what types are
>>>>> underlined in red and where (i.e. in what projects or assemblies)
>>>>> are they declared? Thanks.
>>>>>
>>>>> Regards,
>>>>> Dmitry Shaporenkov
>>>>> JetBrains, Inc
>>>>> http://www.jetbrains.com
>>>>> "Develop with pleasure!"
>>>>>> I take it back... I spoke too soon. I didn't wait long enough for
>>>>>> all the assemblies to be parsed ... everything is underlined in
>>>>>> red again. It doesn't recognize anything. I even deleted the
>>>>>> caches and restarted. That fixed some things, but not everything.
>>>>>>
>>>>>> Lots of "Ambiguous references" that aren't ambiguous at all.
>>>>>>
>>>>>> I'm might have to have to roll back to build 229 again. 331 is
>>>>>> better than 330 I think, but still... I'll try and continue using
>>>>>> for
>>>>>> a little longer and see what happens.
>>>>>> "alastair" <no_reply@jetbrains.com> wrote in message
>>>>>> news:4033282.1143665883446.JavaMail.itn@is.intellij.net...
>>>>>>> try 231, it's out now.
>>>>>>>
>



0

Please sign in to leave a comment.