Patrick Steele's .NET Blog

Ever wanted to single-step through IL code? I haven't myself, but someone else did and Microsoft's Serge Lidin shows you how.

Paul Vick left a comment to my original post explaining that he's having DNS problems and they should be cleared up in the next few days.

Anyone else notice that Paul Vick's blog is gone? It appears the domain name has been scooped up by someone else (it redirects to qp.org -- but whois still shows Paul as the owner). Hopefully he'll start up again at blogs.msdn.com.

I recently wrote an article for 15Seconds.com and it has been published today. Check out "COM Interop Exposed" and let me know your opinions. I plan on doing a follow-up article on exposing .NET events to COM clients (i.e. COM's Connection Point Protocol -- IConnectionPoint, IConnectionPointContainer, etc...).

While researching a question someone asked, I discovered that TLBEXP will "flatten" out your .NET interface hierarchy.

How ironic! I was googling today for something .NET related and came across a link to my old Radio weblog. I clicked on the link and read my last post. It mentioned my move to weblogs.asp.net -- and it was dated one year ago today! Anyway, it's been a great year with .Text and I've never had any problems like I used to with Radio. Thanks Scott!

Suppose you have an architecture where you expose interfaces to your clients and they can create their own COM objects to extend your application by simply implementing one of your interfaces. You don't force them to use a particular ProgID (they may have multiple objects that implement the same interface). Instead, the ProgIDs are stored somewhere (database, XML file, whatever).

Ted Graham posts about determing if an assembly is a debug assembly or a release assembly. His solution was to use the AssemblyDescription attribute: