Problem finding type

I think this relates to the fact that some of the files aren't being correctly
scanned at some point, but I am hovering on a call to a constructor at the
moment that is showing an error in R# (compiles and runs fine).

So, I press to find the constructor - nothing happens So, I press and find the class (it is there) and press ]]>
- VS throws an exception ArgumentException: element == null
Not caught by R# and not fatal - just shown in a little dialog in VS
So I OK that and manually find the class
Which is FULL of R# errors!!!
I change 1 thing and undo - class goes 'green'

Back in original file everything is now ok
<Ctrl-B> and <Ctrl-N> now work fine!

R#203 VS2003

Ronnie


2 comments
Comment actions Permalink

Hello Ronnie,

if you reopen the solution, does this help to get rid of the errors?


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

I think this relates to the fact that some of the files aren't being
correctly scanned at some point, but I am hovering on a call to a
constructor at the moment that is showing an error in R# (compiles and
runs fine).

So, I press <ctrl-B> to find the constructor - nothing happens
So, I press <ctrl-N> and find the class (it is there) and press
<Return>
- VS throws an exception [ArgumentException: element == null ||
!element.IsValid()]
Not caught by R# and not fatal - just shown in a little dialog in VS
So I OK that and manually find the class
Which is FULL of R# errors!!!
I change 1 thing and undo - class goes 'green'
Back in original file everything is now ok
<Ctrl-B> and <Ctrl-N> now work fine!
R#203 VS2003

Ronnie



0
Comment actions Permalink

Hello Dmitry,

I think so - will confirm next time I find one!
It seems to be that some of the currently open files have not been scanned
- am wondering if this problem only occurs if the solution was closed with
open files and then opened - hmm, this last bout seemed to be after a namespace
rename through R# that left several files open unsaved in the editor, but
can't be sure.

Will add more here as and when I discover it

Ronnie

Hello Ronnie,

if you reopen the solution, does this help to get rid of the errors?

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

>> I think this relates to the fact that some of the files aren't being
>> correctly scanned at some point, but I am hovering on a call to a
>> constructor at the moment that is showing an error in R# (compiles
>> and runs fine).
>>
>> So, I press to find the constructor - nothing happens >> So, I press and find the class (it is there) and press >> >> - VS throws an exception [ArgumentException: element == null || >> !element.IsValid()] >> Not caught by R# and not fatal - just shown in a little dialog in VS >> So I OK that and manually find the class >> Which is FULL of R# errors!!! >> I change 1 thing and undo - class goes 'green' >> Back in original file everything is now ok >> and now work fine! >> R#203 VS2003 >> Ronnie >>]]>


0

Please sign in to leave a comment.