Welcome to MSDN Blogs Sign in | Join | Help

December 2006 - Posts

Thursday, December 28, 2006 1:32 AM

Fake attach event ordering

When you attach to a managed debuggee (via ICorDebug::DebugActiveProcess), ICorDebug generates a set of fake events designed to bring the debugger up to the current state. The motivation is that it pumps the debugger just as if the debugger was always
Posted by jmstall | 5 Comments
Saturday, December 23, 2006 8:17 PM

C# app to count #ifdef usage

Here's a little tool I wrote to count #ifdef usage in a project. It provides a summary of the #define name and frequency; plus a detailed XML file of each location that the #define occurred at. For example, when applied to this sample file (in directory
Posted by jmstall | 3 Comments
Filed under:
Wednesday, December 20, 2006 2:28 AM

Embed Macros in Help?

Having to meticulously follow detailed instructions is just an accident waiting to happen. Instead of application Help giving such instructions, I wish the Help would just expose Macros to do it for me. I was just using the Help on Application X. I wanted
Posted by jmstall | 0 Comments
Filed under:
Wednesday, December 13, 2006 10:40 PM

Measuring language complexity: Do you need a debugger?

When people are asking for a debugger for language X, practically it means that the usage of language X has gotten sufficiently complicated that mere inspection is insufficient for diagnosing problems. I alluded to this when I said that XML is code .
Posted by jmstall | 2 Comments
Friday, December 08, 2006 12:19 PM

Your feedback: How many types do you ref.emit into a module?

I'm looking for feedback about Ref.Emit usage patterns. When using Ref.Emit , how many types do you generally emit into a single module? Do your scenarios generally use AssemblyBuilderAccess .RunAndSave/.Run? In other words, are you emitting code so that
Posted by jmstall | 5 Comments
Filed under:
Thursday, December 07, 2006 1:03 PM

Interview Tip: Writing test cases

If during a dev interview, you're asked to write a set of test cases for some function you wrote, be sure to have test cases that reach every basic block. In other words, make sure your test cases at least hit every line of code you wrote. For example,
Posted by jmstall | 6 Comments
Filed under:
Tuesday, December 05, 2006 2:33 PM

What I'm reading now: "C++ Template Metaprogramming"

I'm currently reading " C++ Template Metaprogramming ". It's off to a great start. The basic idea (so far) is that: You can write entire algorithms / programs in C++ templates, which are then executed as the compiler instantiates the template. There is
Posted by jmstall | 4 Comments
Filed under:
Monday, December 04, 2006 11:44 AM

Patrick Dussud is blogging!

Patrick Dussud , lead architect of the CLR, is blogging (as other CLR members are already pointing out). Patrick has an amazing insight and understanding far beyond myself and many others. (If memory serves, Chris Brumme used to report to Patrick). If
Posted by jmstall | 0 Comments
Saturday, December 02, 2006 9:39 PM

Random comments about Sytem.Convert class

The System.Convert class is a neat little class in the BCL (mscorlib) for converting between types. vs. IConvertible : The Convert class is tightly coupled with the IConvertible interface. Convert.ChangeType is just a convenience method to delegate to
Posted by jmstall | 7 Comments
 
Page view tracker