The EQATEC Profiler profiles just about everything . NET, including what you need.
The EQATEC Profiler profiles just about everything . NET, including what you need: Full . NET 2.0 and above Windows Phone 7, both Silverlight and XNA apps Silverlight 2.0 and above NET CF 2.0 and above (WinCE, Windows Mobile) Xbox XNA (lacking integrated deployment to Xbox-device, though) Long story short: the only thing it doesn't profile is .
NET 1. X (full/netcf). No other profilers in the World works on this many .
NET platforms. It's also known for being quite easy to use.
1, and the basic version is free. Too bad it doesn't do line-level profiling. – 500 - Internal Server Error Jan 20 at 17:46.
Visual Studio 2010 has a pretty good builtin profiler (only available in the Premium and Ultimate editions though) Another great profiler is dotTrace. I only listed the profilers I know support . Net 4.0 right now, but do take a look at this older question about .
Net profilers. Maybe some of them have recently added support for . Net 4.0 too.In any case, I don't think there are any new profilers out there, since it's a pretty complex topic.
Maruricio: does dotTrace have . NET 4.0 support yet? – John Saunders Apr 5 '10 at 22:38 Unfortunately I can get a free copy of visual studio pro, so I'm stuck using pro – Martin Apr 5 '10 at 22:42 @John: yes, dotTrace 4.0 beta (latest version as of this writing) supports .
Net 4.0 – Mauricio Scheffer Apr 5 '10 at 22:57 @Mauricio: thanks. – John Saunders Apr 5 '10 at 22:58 Unfortunately at £156 dotTrace is way beyond my price range – Martin Apr 5 '107 at 1:14.
SlimTune doesn't currently support . Net4 – Martin Apr 6 '10 at 1:29.
A tremendously under-advertised free profiler is the SharpDevelop Profiler. Screenshot: It is really powerful, and supports the tremendously undocumented PSQL (Profiler SQL as they call it). For example, I can filter all the functions I am interested in by entering this in to the query bar: for f in Functions where f.Name.
Contains("Foo") select f.
Wow, that looks fantastic! – Martin Jan 21 at 0:39.
Everybody wants a profiler, but this low-tech method works just fine.
While it is possible to do this, it's not really viable, you waste too much time. – Mauricio Scheffer Apr 6 '10 at 12:18 @Mauricio Scheffer: It is understandable to have such opinions if it has not been tried. In my experience (and others on SO) it finds problems very quickly, while people are still trying to get their profilers installed, get them running, figure out what the output means, and realize they don't always tell what they need to know.
– Mike Dunlavey Apr 6 '10 at 16:16 ... Here's a list of myths that many profilers are prone to, including the one in VS, if I'm not mistaken: stackoverflow. Com/questions/1777556/alternatives-to-gprof/… – Mike Dunlavey Apr 6 '10 at 16:34 I don't know why you would assume that kind of things about me. I do use low-tech/poor-man profiling methods (in fact I have blogged about one: bugsquash.blogspot.Com/2009/08/…) but I still think a good profiler is better and faster in 99% of the cases, at least for the kind of code I've been handling so far in my short career.
– Mauricio Scheffer Apr 6 '10 at 17:20 @Mauricio Scheffer: Sorry - I know people on SO are just trying to help each other. In my long career I see people trying out motorcycles, Volkswagens, Maseratis, when a rowboat does the job (though it's OK to put a motor on it). It's a different perspective - not a top-down approach of measuring time, and being concerned about accuracy, but rather a bottom-up approach of asking what it is doing and why, on only a rough percentage basis, looking at lines, not functions, and looking at wall-clock time, not CPU time, ignoring irrelevant stuff like recursion.
– Mike Dunlavey Apr 6 '10 at 18:19.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.