I have developed a WebAPI that is deployed direct to Azure in Live and that I deploy to IIS on the local network in development. The WebAPI is one project within a solution of a number of projects which are referenced by the WebAPI.

I followed these instructions to configure and set up debugging by attaching to process running on the local IIS server:


That works well and I can trace into the WebAPI. However as soon as the WebAPI calls a module in another project in the solution, the tracing ends. I know that as the project is separate to the WebAPI that I can set up other ways to test it, and I have, but I’m curious – Is it possible to be able to trace the code throughout the solution in this scenario?

Anonymous Asked question May 13, 2021