Welcome to MSDN Blogs
Sign in
|
Join
|
Help
Mike Stall's .NET Debugging Blog
Notes on Managed Debugging, ICorDebug, and random .NET stuff
This Blog
Syndication
RSS 2.0
Atom 1.0
Search
Go
Tags
binary_diff
Compilers & Languages
Design
dlr
Edit-And-Continue (EnC)
Family
feedback
FuncEval
ICorDebug
Interop (mixed-mode)
interview
linkfest
MDbg
Non-work
Quiz
Random
random .net
reading
Sample Code
Silverlight
Testing
This should be in MSDN
Troubleshooting
versioning
Whidbey (V2.0)
Windows Live
wishlist
Archives
April 2008 (3)
March 2008 (5)
February 2008 (2)
January 2008 (10)
December 2007 (7)
November 2007 (5)
October 2007 (16)
September 2007 (8)
August 2007 (12)
July 2007 (9)
June 2007 (5)
May 2007 (7)
April 2007 (4)
March 2007 (6)
February 2007 (5)
January 2007 (10)
December 2006 (9)
November 2006 (13)
October 2006 (9)
September 2006 (9)
August 2006 (6)
July 2006 (13)
June 2006 (9)
May 2006 (3)
April 2006 (4)
March 2006 (31)
February 2006 (16)
January 2006 (18)
December 2005 (11)
November 2005 (23)
October 2005 (12)
September 2005 (22)
August 2005 (28)
July 2005 (10)
June 2005 (7)
May 2005 (4)
April 2005 (5)
March 2005 (9)
February 2005 (16)
January 2005 (6)
December 2004 (3)
November 2004 (4)
October 2004 (14)
September 2004 (2)
CLR blogs
David Notario (JIT Compiler)
Rick Byers (CLR)
Jonathan Keljo's blog
List of all CLR blogs
David Broman (Profiling)
Thomas Lai's blog
Other Blogs
Andy Pennell's Blog
GreggM's Blog
Steve's Blog
Tim's .NET blog for web developers
Other links
All about MDbg
What's new in v2.0?
Who am I?
ICorDebug/MDbg Forums
Contact me?
August 2006 - Posts
Wednesday, August 30, 2006 11:40 PM
An example of an API versioning problem.
Here's an example of an API versioning problem. In general: Anytime you take two separate concepts and tie them together based off some current implementation assumption, you're going to get trouble when that assumption is broken. The specific example
Posted by
jmstall
|
4 Comments
Filed under:
Design
,
ICorDebug
Friday, August 25, 2006 4:20 PM
Fixing the MDbg / Iron Python extension...
A while ago, we had a sample of Mdbg-Python extension that let you use python to script MDbg. It was based off a pre-release Iron Python, and things have since broken. We updated at least once to keep up with the breaks. We're aware of the problems and
Posted by
jmstall
|
0 Comments
Filed under:
MDbg
Monday, August 21, 2006 11:36 AM
Buzzword bingo
We've all encountered people who use big words just to impress folks. I think the smarter people communicate with succinct phrases that their audience immediately understands and cleverly convey specific concepts. Some of my favorite vocabulary: Future-proofing
Posted by
jmstall
|
3 Comments
Filed under:
Random
Friday, August 11, 2006 11:48 AM
Asking questions on the forums
With the new ICorDebug / MDbg forum , I've decided to temporarily disable the "Contact Me" link on my blog to encourage folks to ask their questions on that forum (or post public comments on relevant blog entries) instead of mailing me personally. My
Posted by
jmstall
|
1 Comments
Filed under:
Random
Wednesday, August 09, 2006 11:25 AM
Cool tool: NDepend
I just saw a free cool tool, NDepend , which analyzes .NET assemblies and lets you get neet metrics. It also lets you run queries like: WARN IF Count > 0 IN SELECT TYPES OUT OF NAMESPACES "System.Xml" WHERE DepthOfIsUsing "System.Xml.XmlChildNodes"
Posted by
jmstall
|
3 Comments
Tuesday, August 01, 2006 11:58 AM
Empty implementation of ICorDebugManagedCallback
I have to implement the ICorDebugManagedCallback interfaces. I wrote up a stub implementation (that just E_NOTIMPLs all the methods) and am posting it here for reference. It's pretty tedious, so I'll post it here and then never have to write that again.
Posted by
jmstall
|
2 Comments
Filed under:
ICorDebug
,
Sample Code