Loren Halvorson's Blog

I've written about this add-in before, but I frequently run into .NET developers who are attempting test driven development without using the free TestDriven.NET Visual Studio .NET add-in.

New releases (RC3) of the excellent NAnt build tool are now available.

Well it seems like the incubating log4net has finally awakened from its slumber.

I'd like to thank Tom Hollander and Hisham Baz for their responses to my post comparing Log4net and the EntLib logging block. Tom did an excellent job of pointing out how every app has different requirements, and it is dangerous to take performance numbers alone as the sole criteria for selecting a technology. I would also like to thank Hisham Baz for taking the time to profile the block and identify some possible optimizations that could be made.

Microsoft recently released 1.0 of the Enterprise Library. I was curious how the Logging block stacked up to Log4net.

Votive for WiX

I've been using the slick little iehttpheaders tool to trace my browser's http traffic when troubleshooting issues. It logs out the requests, responses, cookies, HTTP headers etc... flowing back and forth. But the other day this MSDN article convinced me to spend a couple minutes looking at Fiddler, and I'm so glad I did. All I can say is Wow! This thing is going to come in handy. I wish I'd found it sooner.

One thing I really miss coming to ASP.NET from JSP is a mature application based Model View Controller framework like Struts and Maverick. From what I read this is a common refrain from former Java developers.