The "Tools Library" in our group is DLL which uses many of our internal projects (all C #) I developed intuition Have done that a good part of the tool library is used by only one project - let's call that project "Project A" Tools can examine NLL and all projects (probably Project EXE), and can calculate all the methods and classes in the tool library which can actually be used by Project A. I think there is some redistribution in order (to change the part of the Tool Library to the project's own codebase), and such a list seems to be very useful.
Due to the reflection, I do not think a device can do 100% correctly, but assume that I know that none of our projects are using the Library Library with any clever reflection techniques. Does; They apply it only with the common method call which should be eligible for static analysis.
Looks like a tool to determine if a quick check for you is also available in Visual Studio If you are using, you can right-click on DLL in the project context and select 'Find dependent code' and it will list the use within the same project.
Comments
Post a Comment