dotTrace

What does it mean, dotTrace 4.0 Performance? Where's my memory profiling? Has dotTrace been split into two separate products?

Yes, dotTrace has been split into two products: dotTrace Performance and dotTrace Memory. They will have different license keys and different release cycles. We're releasing dotTrace 4.0 Performance first, and dotTrace 4.0 Memory will follow later this year.

OK, dotTrace 4.0 Performance is excellent news, but what about dotTrace 4.0 Memory?

We're looking to release dotTrace 4.0 Memory in Fall 2010. If you require memory profiling features before then, please feel free to use dotTrace 3.1 in memory profiling mode. dotTrace 4.0 Performance and dotTrace 3.1 can work side-by-side on your machine.

In addition, as soon as dotTrace 4.0 Performance goes from Beta to RTM (or even earlier), we'll make available dotTrace 3.5: an abridged version of dotTrace 3.1 with only the memory profiling features, plus support for CLR4.

I have a dotTrace 3.1 license. Can I upgrade to dotTrace 4.0 Performance for free?

That depends on when you bought it. If you purchased a dotTrace 3.x license after December 17, 2008, you'll be able to upgrade to dotTrace 4.0 Performance + dotTrace 3.5 Memory completely free of charge!

Can I upgrade from dotTrace 3.1 to dotTrace 4.0 Performance and drop the Memory part?

Existing users will only be available to upgrade to the bundle consisting of dotTrace 4.0 Performance and dotTrace 3.5 Memory. We're assuming you need both.

How much will it cost to purchase dotTrace 4.0 Performance, or upgrade to 4.0 Performance + 3.5 Memory?

We'll make available pricing options for new and upgrading users shortly after dotTrace 4.0 Performance Beta release.

dotTrace 4.0 Performance comes in two editions. What's the difference between them?

dotTrace 4.0 Performance Standard Edition provides all the functionality that is available in Professional Edition, excluding support for .NET Compact Framework 3.5, Silverlight 4, and remote profiling.

Can dotTrace attach to a running process and profile it?

No, and we’re not planning to add such functionality in the near future because of technical limitations in the profiling API.

I have a function that took 1450 ms and was called 214 times. Is this the average time per call or the total time for all calls?

This time is always a total. Average time is shown in Quick Info window which can be invoked from the context menu (or by pressing Ctrl + Q).