![]() ![]() NET (unlike Visual Studio) supports the notion of multi-module assembly creation bound to several “ modules”. ![]() I’m sure that most of you know what an assembly is: this is what gets generated when you compile a Class Library in Visual Studio. This post deals with the notions of module, assembly and type in addition to introducing the. the assembly where the method type is defined), the type name, the method name and the list of its parameters type and name. You will have to get the module name (i.e. ProfilingTest.dll!PublicClass.ClassParamReturnClass(ClassType obj) Unlike what you might think, this first question is not an easy one, especially if you would like to get the complete signature of the method such as what you get in Visual Studio Call Stack panel: So what if you would like to know the name of the method behind this FunctionID? For us, it is just an opaque value that is usable in different CLR APIs. ![]() As David Broman (source of most of the profiling implementation details at Microsoft) explains, a FunctionID is a pointer to an internal data structure of the CLR called a MethodDesc. In the first post of this series dedicated to CLR Profiling API, you have seen how to get a FunctionID each time a managed method is executed in a. ![]() Dealing with Modules, Assemblies and Types with CLR Profiling APIs Introduction ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |