This post originated from an RSS feed registered with .NET Buzz by Duncan Mackenzie. Original Post: CLR SPY Feed Title: Code/Tea/Etc... Feed URL: /msdnerror.htm?aspxerrorpath=/duncanma/rss.aspx Feed Description: Duncan is the Visual Basic Content Strategist at MSDN, the editor of the Visual Basic Developer Center (http://msdn.microsoft.com/vbasic), and the author of the "Coding 4 Fun" column on MSDN (http://msdn.microsoft.com/vbasic/using/columns/code4fun/default.aspx). While typically Visual Basic focused, his blogs sometimes wanders off of the technical path and into various musing of his troubled mind. Latest .NET Buzz Posts Latest .NET Buzz Posts by Duncan Mackenzie Latest Posts From Code/Tea/Etc...

CLR SPY: Feature requests for the next version

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!