How to find all the references to a method in different solutions.

Question

0.00/5 (No votes)

See more:

We have different modules in our project. Each module implemented as separate solution. There are 40+ solution in the project. I am making a change to one method in one solution eg. Enctypt() method. It is a overloaded method and it is being used in many places in different solutions. I want to find out all the places where this method is referenced.

Is there a best way / any tool available to find all the references to a method in different solutions.

What I have tried:

I tried to search for Encrypt() method in all the solutions but it returned thousands of results. because there are method with same name available in other solutions also, hens it is returning many results.

I tried to search with namespace and class name also.

your valuable suggestion will be very helpful to me. Thanks.

Posted 19-Oct-16 20:50pm

naveen_g

Updated 20-Oct-16 0:11am

Add a Solution

3 solutions

Solution 1

I think you are confusing "Solution" and "Project" - Visual Studio loads a single Solution, which can consists of multiple Projects: each Project generates a separate Assembly.
Within a Solution, you can go to the definition of a method, right click it's name, and select "Find All References" to get a complete list of everywhere it is used within the Solution.

If however, this is multiple Solutions, then there is AFAIK no built in method to locate all references in all Solutions of a single method - if only because Projects with use References to an Assembly (rather than a Project) do not have any back-links to the Assembly source.

Posted 19-Oct-16 21:10pm

OriginalGriff

Solution 2

Hi naveen_g

How you ever keep things together if you organize your solutions like this, I wonder?
What I do: Only work with project references inside solutions, no assembly-references to your own projects.
Then I group the projects together in the solutions I need them (it's perfectly valid to have a project take part in different solutions).
Then layer/group your solutions - Kind of "staging" for references (e.g. I use Shared, Service, Client, Data, Hardware, Gateway) so that the least possible project-overlap is created.
-> And problems like yours should be very seldom...

Then if you have a build-system in place and use CI you will find out on validation-build you broke one of the staged (then assembly-referenced) solutions (all solution concerned should be build by your builddefinition of course).

But I have to confess it was a long and painfull way to organize everything like that and find a nice workflow that everyone can keep up with...

So maybe a simpler solution could be (depends how many projects you really have) make one big 'dummy' solution for all your projects (this one will be just for cases like you have now, just don't forget to add new projects there also, if you create new solutions or add projects to existing ones later.

Kind regards

Johannes

Posted 19-Oct-16 23:44pm

johannesnestler

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

F-ES Sitecore · Accepted Answer · 2016-10-20T00:11:00

Solution 3

Load all projects into one solution and have them reference each other by project reference. If that's not possible\too much effort, download a tool called IL Spy, load all your assemblies into it and use its "Analyze" feature to show you what methods call what.

Posted 20-Oct-16 0:11am

F-ES Sitecore