profiling non-.net applications ?

[sajanisch]

okay, this is probably a crazy question, but...

I was under the impression from coworkers that this could be used on non-.net applications...is that true ?

I see the information about tracking unmanaged resources but I can't seem to attach to a unmanaged application

thanks, Scott

[Andreas Suurkuusk]

Even though .NET Memory Profiler can profile unmanaged resources, the profiler is not actually activated until the .NET runtime has been loaded into the process. Therefore it is currently not possible to profile a non-.NET application. We have actually planned to allow non-.NET processes to be profiled since version 3.0, but other features have been prioritized. Hopefully we will implement this for version 4.1.

[sajanisch]

Do you have any estimate as to when a 4.1 version will be available (even if beta) ?

Also, what if I can create a .NET application that uses my native dll ?
(would my memory/profiling work on the native dll ?)

thanks, Scott

[Andreas Suurkuusk]

We have not yet decided on the feature set of version 4.1, so it's still too early to make an estimate of the release date. However, our plan is to use shorter release cycles than previously and tol be able to release the next version within 6 months of the version 4.0 release.

If your native dll is loaded by a .NET application, you will be able to profile your dll using .NET Memory Profiler. Actually, to force the profiler to connect to a native application, you can use the .NET hosting API to load the .NET runtime into the process, without actually using .NET.