Does your project rely on a number of externals--things in the GAC, COM+ packages, registry keys and the like? Do your unit tests need these? What tricks do you use to set up your environment for unit testing? I've resorted to a number of dirty tricks...

My friend J Sawyer and I are doing an article for November's MSDN...the title's not fixed but it's something like "Real-World Cryptography". J's a Developer Evangelist down here in Houston, and he's one of the finest developers I know. Nevermind that...

Wish me luck. I'm about to start a flame-war. At issue: VB tries too hard to "help" you--but sometimes gets in the way at the worst possible moments. In Evidence: I'm on a fairly complex project involving web services, COM+ ServicedComponents, heavy-duty...

First off, I wish C#Refactory were available for VB.NET!!! ARRGHH! I've become so enamored of C#Refactory (find it at http://www.xtreme-simplicity.net/ ). It's one of those tools you use for a week and realize it's already paid for itself, a slam-dunk...

First, please go to: http://workspaces.gotdotnet.com/busybeebuilder There, you can download my favorite pet project the BusyBeeBuilder. The MSI installs the binaries, source, and docs. It's a clean install--and it uninstalls cleanly too. I'm a HUGE fan...

No weird existential answers yet, I'll save those for later. But just to pique your curiosity, I think it's highly likely we are in fact simulations running on a fairly competent workstation in a far future historian's simulation software. The funny stuff...

I've delayed starting a blog for 2 years now. I figured by this time it's no longer a fad; after all I'm too cool to just join any old fad! No, I join fads when they're well-established and on their way out. This, my soon-to-be friends, is the secret...