You are right, it is a limitation in that 1) you can only use one profiler at a time 2) attaching the profiler is somewhat tedious 3) the unmanaged APIs are less than friendly to be used.
But so far it is the only solution to runtime-manipulation of existing code and metadata (unless I am missing something). Does anyone know, why exactly it isn't possible to turn a loaded assembly/module/type into a dynamic assembly/module/type? Also, if it were possible to implement a custom loader, life would be much easier regarding runtime code extension. Fabian Schmied -----Ursprüngliche Nachricht----- Von: Thomas Tomiczek [mailto:[EMAIL PROTECTED] Gesendet: Mo 24.03.2003 14:04 An: [EMAIL PROTECTED] Cc: Betreff: Re: [ADVANCED-DOTNET] Adding a custom attribute to a type This is a very bad solution under most circumstances - NORMALLY you would want your program not to run under the profiler. I face similar limitations in other situations (the need to replace a method's bytecode at load time), and I found having the profiler running during program run not to be acceptable. Regards Thomas Tomiczek THONA Consulting Ltd. (Microsoft MVP C#/.NET) =================================== This list is hosted by DevelopMentor® http://www.develop.com You may be interested in Guerrilla .NET, 24 March 2003, in London and Boston http://www.develop.com/courses/gdotnet View archives and manage your subscription(s) at http://discuss.develop.com
