Profiler doesn´t work with Framework 2.0.50110

[ragnar88]

I want too use your profiler to profile an application with is compiled under the .Net Framework v2.0.50110, but when I start the profiling session the profiler says “Waiting for profiled process to start.” and nothing more happens even when I end the application. But the profiler is still working and I can press “Cancel” to stop the profiler. I use the profiler Version 2.5.28.0 under Windows XP Pro SP2. I already tried to put the Framework Version in the configfile as supported runtime but nothing changed.

[Andreas Suurkuusk]

There has been a change in the way a profiler attaches to a .NET process in build 2.0.50110. Due to this change .NET Memory Profiler cannot profile a process using this build.

We will fix this issue and release a new version during the next week.

[Andreas Suurkuusk]

We have just released a new version (v2.5.29) of the profiler, but unfortunately it still doesn't support .NET Framework build 2.0.50110. Even though we could easily get our profiler to run under this build, there are some issues that we have to deal with, due to some breaking changes in the Profiler API.

We are working on it and will soon be able to release a version that supports 2.0.50110.

[ragnar88]

Hi,

When will the new Version be released? I hope before Beta2 because I NEED IT !!!!!!!

Thanks,
Gino

[Andreas Suurkuusk]

We're experiencing some dead-lock issues that we have still not resolved. The problem is that we can hardly use the February CTP of Visual Studio.NET 2005, since it becomes extremely slow after having run one debugging session and it crashes very often. We will continue to try to solve the issues, but due to the problems mentioned I'm not sure that we can solve them until beta 2 is released (which it hopefully will be soon).

[Andreas Suurkuusk]

Now we have released v2.6 of .NET Memory Profiler. This version includes full support for .NET Framework 2.0 (v2.0.20727 (RC1)). It will also work against .NET Framework 2.0.20215 (beta 2), but roots will not be identified.

The new version can be downloaded from: http://memprofiler.com/download.aspx.

[bmwaustin]

Do you guys have a version for .Net 3.5 Framework?

[Andreas Suurkuusk]

Yes, both .NET Memory Profiler 3.0 and .NET Memory Profiler 3.1 works with .NET Framework 3.5. Are you experiencing any problems running against .NET Framework 3.5?