Freigeben über

CLR SPY: Feature requests for the next version

  • Artikel

Now that I'm set up at my new blogging home, I'd like to get some feedback from anyone who has used the CLR SPY tool that I've uploaded to gotdotnet.com and blogged a lot about in the past.

We're investigating shipping the tool in the .NET Framework SDK, and would like some feedback on what you do/don't find useful about it.  The Whidbey CLR will have a larger set of CLR Debug Probes (CDPs) than what v1.1 has, and these will all be exposed in the updated tool, of course.  But do find the “monitoring“ behavior of the tool useful?  Are the balloon notifications annoying?  etc. etc.

Thank you in advance!

Comments

  • Anonymous
    January 13, 2004
    How about a CDP for calling code on the wrong thread? This is particularly relevant to Windows Forms code. Would it be possible to do a CDP for not calling EndInvoke on a delegate?

    The ballon notifications but in the end what I really want is a report listing all the problems. The log is OK for that but I'd rather be able to pull up the ClrSpy UI and see a history/log of issues.
  • Anonymous
    January 13, 2004
    Thanks, Keith. Ian Griffiths also asked for such a CDP here: http://blogs.msdn.com/adam_nathan/archive/2003/08/23/56745.aspx We'll see what can be done. I'll pass along both of your requests.

    Yes, I'm definitely planning to have a simple table that logs all messages that you can clear, sort, etc.
  • Anonymous
    January 21, 2004
    The comment has been removed
  • Anonymous
    February 16, 2004
    The comment has been removed
  • Anonymous
    March 09, 2004
    I'm working on an OPSEC LEA client. Rather stupidly, they need you to reference struct pointers in their DLL's.

    I'm getting around this at the moment by going

    #pragma unmanaged

    __declspec( dllimport ) extern OpsecEntityType *LEA_CLIENT;
    __declspec( dllimport ) extern OpsecEntityType *LEA_SERVER;

    #pragma managed

    I'd like clearer documentation on

    a) if this is supported

    a2) if not, why it's a really good idea to refactor your code to use accessor functions

    a3) If yes, how to do this in a supported way, linked off a related links page in MSDN or platform SDK.

    DllImportAttribute and the marshalling area of P/Invoke simply don't go into it at all, and it's the sort of gotchya that will make or break some projects.

    Andrew
  • Anonymous
    March 09, 2004
    Whoops - wrong wish list. :)
  • Anonymous
    April 11, 2004
    LOL
  • Anonymous
    April 11, 2004
    Free books for students, teachers, and the classic enthusiast.
  • Anonymous
    April 19, 2004
    [whinge-moan-gripe]
    Pinvoke.net doesnt work in Firefox!
    [/whinge-moan-gripe]
  • Anonymous
    May 30, 2004
    The comment has been removed
  • Anonymous
    June 04, 2004
    good
  • Anonymous
    July 25, 2004
    dianying xia zai:http://www.kamun.com/
    movie down:http://movie.kamun.com/
    mp3 xia zai:http://music.kamun.com/
    engage:http://club.kamun.com/
  • Anonymous
    July 27, 2004
    The comment has been removed