Hi! Obviously Cecil can only help with what's statically discoverable :)
For runtime scenarios, only a profiler can give you the actual path the code is taking. There's no easy way to trace say a WCF call to a remote WebService, at some point you'll have to manually link a caller in the client to a callee on the server. Jb On Wed, Apr 22, 2015 at 8:47 PM, Diogo Oliveira <[email protected]> wrote: > Hi, > > I'm using Mono.Cecil to build a call hierarchy in my program. It's a complex > program and what I want to do is: having method A(), what are all directly > on indirectly methods that might be called from A's execution? > > In fact, at this moment I already achieved this. > > My question is the following: imagine I have a client application and some > services / web applications. They may use remoting, WCF calls, etc. > > Is there any way I can possibly trace the call hierarchy in these > situations? Since this is static analysis and late binding / WCF calls are > runtime events. > > Thanks in advance! > > Best Regards, > Diogo > > -- > -- > -- > mono-cecil > --- > You received this message because you are subscribed to the Google Groups > "mono-cecil" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- -- -- mono-cecil --- You received this message because you are subscribed to the Google Groups "mono-cecil" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
