Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I'm working with the profiling API so most of my comments are about the CLR profiler.<br> The MSDN documentation is quit bad. You get a general description of the what a method or a class is doing and a short description of the method arguments that's it. No examples.<br> If you are lucky you can find some blog about your problem. </p> <p>Some links that can be helpful with the profiler API are:<br> <a href="http://msdn.microsoft.com/en-us/magazine/cc300553.aspx" rel="nofollow noreferrer">This MSDN magazine artical</a> - old but a good starting point.<br> <a href="http://blogs.msdn.com/davbr/default.aspx" rel="nofollow noreferrer">David Borman's blog</a> - Does not update very often but the information worth gold :)<br> <a href="http://blogs.msdn.com/clrteam/default.aspx" rel="nofollow noreferrer">The CLR team blog</a> - Update few times a month.<br> Rotor The <a href="http://www.microsoft.com/downloads/details.aspx?FamilyId=8C09FD61-3F26-4555-AE17-3121B4F51D4D&amp;displaylang=en" rel="nofollow noreferrer">CLR source code</a><br> And you can always try to mail the CLR team if you get stuck they actually been very helpful when we needed their help.</p> <p>About the compatibility issues: Not sure I understand what you are asking here, what I do know is this:<br> If you don't have to support previous versions go to the latest CLR 4. CLR 4 includes some major changes (few instances of the CLR can run side by side in the same process) read <a href="http://blogs.msdn.com/davbr/archive/2008/11/10/new-stuff-in-profiling-api-for-upcoming-clr-4-0.aspx" rel="nofollow noreferrer">this post</a> and decide how you should deal with it. </p> <blockquote> <p>my system would require the debugger be implemented in managed code &amp; managed API, and the existing ones are written in unmanaged code.</p> </blockquote> <p>As far as I know you can download the source code of managed wrapper API for the debugger API. (Can't find the link right now)</p> <p>Hope it helps.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload