A question on the new CLR Profiler for .NET Framework 2.0 Beta2

I notice that there is a new release of CLR Profiler for .NET Framework 2.0 Beta2. However, there is also a profiler in Whidbey Team System Beta2. What's the difference between them? Which one should I use?

Thanks!

[217 byte] By [LeiJiang] at [2008-2-12]
# 1
Hi Lei Jiang,

CLRProfiler is a specialized tool that allows you to analyze in detail the allocation behavior of your application - what it allocates, how long object instances stay around before they are cleaned up by the garbage collector, etc.

The profiler in Whidbey Team System in contrast is more general - it allows you to see where your program spends its time as well see the allocation behavior.

So the focus of the two tools is quite different. Perhaps it would make sense to start with the profiler in Whidbey Team System, and use CLRProfiler if you need more detailed analysis of the allocation behavior.

Thanks
Peter

PeterSollich at 2007-9-9 > top of Msdn Tech,.NET Development,Common Language Runtime...
# 2
Could the CLR Profiler be integerated into VSTS? So the user will not have to learn two tools and switch between them.
LeiJiang at 2007-9-9 > top of Msdn Tech,.NET Development,Common Language Runtime...
# 3
To a certain extent this is what has happened - the VSTS folks have looked at CLRProfiler and integrated the most important features into VSTS.

The idea was that most users would just work with VSTS.

Thanks
Peter

PeterSollich at 2007-9-9 > top of Msdn Tech,.NET Development,Common Language Runtime...
# 4
It's a great news :-)
LeiJiang at 2007-9-9 > top of Msdn Tech,.NET Development,Common Language Runtime...

.NET Development

Site Classified