We have a .NET assembly that is hosted as a snap-in inside MMC via Ironring Software's MMCLib wrapper. We have recently noticed a performance issue in our snap-in and have been trying to use the ANTS profiler to diagnose. We set up mmc.exe as the executable to profile, and selected to profile All .NET Methods in the configuration wizard. When we attempt to start profiling, we receive a warning message that mmc.exe is not a .NET executable. We click OK and MMC does run. We let the snap-in run for a few minutes, then we shut down MMC. At this point, the ANTS profiler never notices that MMC is no longer running (i.e. it thinks that we're still profiling, even after MMC has been terminated for 30 minutes). If we manually stop profiling, we get no results.
Are we setting something up incorrectly, or is there an issue with profiling a .NET assembly hosted inside a native-mode executable?