The "Profile Verification" function in Visual Studio 2013 will only be a tool assembly created by profiling unit test, and will only report function calls in the libraries of this solution. It will not profile or report any function calls that come from peer-reviewed libraries created by other solutions.
I have a Visual Studio 2013 solution with some C # library projects and some C # unit test projects. The code refers to additional C # libraries that are produced by several other VS2013 solutions (think of application code that uses the framework where the application is in one solution and the environment is in another solution).
When I run the "Profile Verification" operation, I see the message "** Instrumented C: ... \ something.dll **", etc. in the window of the output window. Only DLLs created by this solution are written.
Therefore, I suppose that the profiler does not report calls in assemblies built by another solution, because they are not "instrumental".
Is there a way to create tool assemblies that can be referenced by another solution? (I looked, but did not find such an option.)
- Dave Hane