Determining exactly which part of an application is making HTTP requests can be difficult when it depends upon obfuscated 3rd-party libraries.
It would be incredibly useful to be able to give ClrSpy a list of fully-qualified method names to watch and have it log every single call plus full stack trace.
(Specific use case: trying to determine exactly where I've missed overriding a ResourceLoadingCallback in an application which uses a 3rd-party library to generate Word documents from HTML)
Determining exactly which part of an application is making HTTP requests can be difficult when it depends upon obfuscated 3rd-party libraries.
It would be incredibly useful to be able to give ClrSpy a list of fully-qualified method names to watch and have it log every single call plus full stack trace.
(Specific use case: trying to determine exactly where I've missed overriding a ResourceLoadingCallback in an application which uses a 3rd-party library to generate Word documents from HTML)