I agree with Fabian ... The last time I checked the CLR would not code pitch and re-jit all the already JIT'ed methods if you were to connect a profiler later (connecting a profiler changes the JIT'ed code of methods). This would be a really sweet feature to add though if anyone from MS is listening here :)
That said most of the runtime AOP frameworks also do not allow 'real-time' changes most force you to restart the app. Cheers, Greg On 10/10/07, Fabian Schmied <[EMAIL PROTECTED]> wrote: > > 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 DevelopMentor(r) http://www.develop.com > > View archives and manage your subscription(s) at http://discuss.develop.com > -- Studying for the Turing test =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
