Is there any kind of file dependency tracer for Asp.Net apps?

Question

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

Answer 1

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.

Answer 2

I've used AutomatedQA's AQTime do this kind of thing. You can view sequence diagrams, call graphs, etc.... From there you can see which assemblies and files are being used.

They have a free trial that will give you plenty of time to do what you need to do.

Answer 3

MZ Tools 6.0 integrates with Visual Studio and has a "get callers" type feature. http://www.mztools.com/v6/mztools6.aspx

Answer 4

I would just move the ascx control to a new project and debug stuff one by one. Then, I would compile that into a dll and use it in the different project.

Answer 5

Have you tried NDepend? There's a plugin for Reflector as well.

Answer 6

Nope. There's no way to do that.