Filtering code profiling by function or module

[mscarlos]

Is there a way that one can exclude certain functions during code profiling? A sample scenario is profiling integration tests where most of the time is spent prepping up data (e.g., database inserts). I would like these calls excluded from the report since I'm not really interested on these methods. On another level is exclusion of certain modules (e.g., System.Windows.Forms.dll); again the reports show a lot of method calls from these modules which I don't want to see at the moment.

[Andreas Suurkuusk]

In .NET Memory Profiler 3.5 it will be possible to group allocations by assembly, namespace, and type (see screenshot below). The bottom part shows the details (e.g. allocations and live instances created by the selected assembly/namespace/type/method). From there you can view the details of the specific instances. Is this the type of presentation you need?