Yes, you are correct. I got my hands dirty with CLR Profiler 1.1 and it gives quite a bit of information about the current state of the process and memory. It also gives information about the method calls. Although the call graph is not that good, still it will do till the time I don't figure out any other good tool or write my own.
Thanks for writing. Cheers, Girish Jain -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Fabian Schmied Sent: 10/10/2007 1:21 PM To: [email protected] Subject: Re: [ADVANCED-DOTNET] AOP with .NET and logging method calls > Given your constraints, you should investigate the .NET Profiling APIs. Or, if you really need to attach to a running process with not preparations whatsoever, you'd probably have to write a debugger (i.e. use the Debugging API). As far as I recall, a profiler must be activated before the process is started. (Though my experience is from the version 1.1 Profiling API.) Fabian =================================== This list is hosted by DevelopMentorR http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
