I have an Asp.Net 2.0 (VB.Net) app and I'm trying to export a Control (ASCX) to another project. I need to know what other files that the Control needs in order to work.
Is there any way - using VS.Net 2005 or an external app - to recursively trace the dependencies of a page or control in a solution?
For example, for this file: ~/Controls/SomeControl.ascx
, I'd like to get the following list of files that it depends on to run:
~/Controls/SomeControl.ascx
~/Controls/SomeControl.ascx.vb
~/App_Code/SomeClass.vb
~/App_Code/AnotherClass.vb
~/App_WebReferences/com/example/SomeWebService/SomeWebService.disco
~/App_WebReferences/com/example/SomeWebService/SomeWebService.discomap
~/App_WebReferences/com/example/SomeWebService/SomeWebService.wsdl
~/App_Code/AnotherClass.vb
I've used the Assembly Binding Log Viewer (Fuslogvw.exe) or maybe ProcMon...
One of my coworkers suggested this app called Dependency Auditor. I haven't used it though and am not vouching for it necessarily.
MZ Tools 6.0 integrates with Visual Studio and has a "get callers" type feature. http://www.mztools.com/v6/mztools6.aspx
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With