Find Usages problems

Something has obviously changed in the implementation of "Find Usages". I'm
using build 202 on VS.Net 2003.

I have a solution that has a LOT of projects. I'm changing a method
signature that I know for a fact is used in four different projects within
this solution. Find usages on the API itself will only find the usages in
that project. If I find usages on one of the other usages, it finds the
usages in the other three projects, but not the project that defines the
API.

Wha??

This worked fine in Resharper 1.5

To be more explicitly clear, say I have a solution with 26 projects, A
thorugh Z.

Method Bar() on type Foo is defined in project C.

Projects M, N, and X all reference Foo.Bar();

If I put the cursor on "Bar" in project C, where it's defined, all I get are
references within project C (regardless of whether I use plain old Find
Usages, or Find Usages (advanced) ... but in this case, I'm using the
Advanced, because there are a few overloads I also want to find).

If I place the cursor on "Bar" where it's used in project M, then I find the
usages in projects M, N, and X.

This is bad. Real bad. It means the refactoring isn't working across
projects the way it should.


3 comments
Comment actions Permalink

Hello Paul,

I have recollections that we discussed similar problems when using assembly
references instead of
project references. In ReSharper 1.0 refactoring didn't work across projects
when you use assembly references.
There were fixes in ReSharper 1.5 which amended this situation. Those fixes
have not been incorporated into 2.0
yet - we're going to do that in near future.

Please correct me if I'm confusing something.

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

Something has obviously changed in the implementation of "Find
Usages". I'm using build 202 on VS.Net 2003.

I have a solution that has a LOT of projects. I'm changing a method
signature that I know for a fact is used in four different projects
within this solution. Find usages on the API itself will only find
the usages in that project. If I find usages on one of the other
usages, it finds the usages in the other three projects, but not the
project that defines the API.

Wha??

This worked fine in Resharper 1.5

To be more explicitly clear, say I have a solution with 26 projects, A
thorugh Z.

Method Bar() on type Foo is defined in project C.

Projects M, N, and X all reference Foo.Bar();

If I put the cursor on "Bar" in project C, where it's defined, all I
get are references within project C (regardless of whether I use plain
old Find Usages, or Find Usages (advanced) ... but in this case, I'm
using the Advanced, because there are a few overloads I also want to
find).

If I place the cursor on "Bar" where it's used in project M, then I
find the usages in projects M, N, and X.

This is bad. Real bad. It means the refactoring isn't working across
projects the way it should.



0
Comment actions Permalink

Paul: I've found your post in another thread 'Had to revert back to 1.5' that
gives me confidence that I'm right and the problem you're describing indeed
relates
to references issue.

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

Hello Paul,

I have recollections that we discussed similar problems when using
assembly
references instead of
project references. In ReSharper 1.0 refactoring didn't work across
projects
when you use assembly references.
There were fixes in ReSharper 1.5 which amended this situation. Those
fixes
have not been incorporated into 2.0
yet - we're going to do that in near future.
Please correct me if I'm confusing something.

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

>> Something has obviously changed in the implementation of "Find
>> Usages". I'm using build 202 on VS.Net 2003.
>>
>> I have a solution that has a LOT of projects. I'm changing a method
>> signature that I know for a fact is used in four different projects
>> within this solution. Find usages on the API itself will only find
>> the usages in that project. If I find usages on one of the other
>> usages, it finds the usages in the other three projects, but not the
>> project that defines the API.
>>
>> Wha??
>>
>> This worked fine in Resharper 1.5
>>
>> To be more explicitly clear, say I have a solution with 26 projects,
>> A thorugh Z.
>>
>> Method Bar() on type Foo is defined in project C.
>>
>> Projects M, N, and X all reference Foo.Bar();
>>
>> If I put the cursor on "Bar" in project C, where it's defined, all I
>> get are references within project C (regardless of whether I use
>> plain old Find Usages, or Find Usages (advanced) ... but in this
>> case, I'm using the Advanced, because there are a few overloads I
>> also want to find).
>>
>> If I place the cursor on "Bar" where it's used in project M, then I
>> find the usages in projects M, N, and X.
>>
>> This is bad. Real bad. It means the refactoring isn't working
>> across projects the way it should.
>>


0
Comment actions Permalink

Yes, you are exactly right. Good to know. Thanks!


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

Hello Paul,

>

I have recollections that we discussed similar problems when using
assembly references instead of
project references. In ReSharper 1.0 refactoring didn't work across
projects when you use assembly references.
There were fixes in ReSharper 1.5 which amended this situation. Those
fixes have not been incorporated into 2.0
yet - we're going to do that in near future.

>

Please correct me if I'm confusing something.

>

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

>
>> Something has obviously changed in the implementation of "Find
>> Usages". I'm using build 202 on VS.Net 2003.
>>
>> I have a solution that has a LOT of projects. I'm changing a method
>> signature that I know for a fact is used in four different projects
>> within this solution. Find usages on the API itself will only find
>> the usages in that project. If I find usages on one of the other
>> usages, it finds the usages in the other three projects, but not the
>> project that defines the API.
>>
>> Wha??
>>
>> This worked fine in Resharper 1.5
>>
>> To be more explicitly clear, say I have a solution with 26 projects, A
>> thorugh Z.
>>
>> Method Bar() on type Foo is defined in project C.
>>
>> Projects M, N, and X all reference Foo.Bar();
>>
>> If I put the cursor on "Bar" in project C, where it's defined, all I
>> get are references within project C (regardless of whether I use plain
>> old Find Usages, or Find Usages (advanced) ... but in this case, I'm
>> using the Advanced, because there are a few overloads I also want to
>> find).
>>
>> If I place the cursor on "Bar" where it's used in project M, then I
>> find the usages in projects M, N, and X.
>>
>> This is bad. Real bad. It means the refactoring isn't working across
>> projects the way it should.
>>
>



0

Please sign in to leave a comment.