sfeldman.NET

HttpListener provided with .NET version 2.0 and up allow to build a custom HTTP server based application without need to have IIS installed on machine. This can be handy in some scenarios, where IIS cannot fit it. HttpListener can handle normal HTTP traffic, as well as HTTPS (secure). Once details that is hard to find online, is the fact that there’s a conflict between IIS and HttpListener to listen simultaneously to port 443 despite different prefixes being used. After digging for a while, the answer was found. Apparently, Windows 2003 is coming with IIS 6.0 and Windows XP comes with IIS 5.1. That little details does the difference (underlying implementation in HTTP.SYS looks like).

This is personal content post.

If you are from Calgary area, and willing to join .NET team for enterprise development – let me know. We are using .NET, BDD development style, not bleeding, but quite on the edge. If you like to develop quality software, and agile process is what you want, send me your resume at feldman [dot] sean [dot] work [at] gmail [dot] com.

This is really funny. A friend of mine forwarded a link, where a little Windows 7 trick is described to get management links in one folder for Windows 7 system. Steps to reproduce are simple:

log4net is a great facility to create logs. When it comes to extending it, it’s good as well. To add a custom property to a custom appender that can be configured from configuration XML file is so simple, that it even looks suspicious.

We are a TDD shop, or BDD to be more accurate. Normally we leverage Hudson Test Result Trend to see how things are doing. The project is a Windows NT Service. This is how Test trend looks like:

While working on a specific task that required a lot of parsing, I came to conclusion that comments for Regex expressions are quite useful. The way I usually write code allows to look at specifications and determine what each component can do. But with Regex it’s not quite transparent, as you might use expressions to achieve the goal, but not necessarily expose the usage through specs.

Daniel Cazzulino had a very helpful post about how to mock extension methods. The only part I don’t like about this method is the fact you have to make internals visible to the test assembly using an assembly directive: