I typically work in a consulting capacity and work on a lot of projects. Because of this, I am continually reorganizing projects and adding open source projects to aid in development. I finally decided it was time to document this directory structure so I don't have to pull it from memory with every project.

As I mentioned before, it was hard to find information on how to setup an ASP.NET HTTP handler when I first started out. Of course, after time, I've found a wealth of articles, posts, and comments from others on these and other related topics. As my second post in the HTTP module/handler saga, I hope to give you an in-depth discussion on the topic of handlers to include pros, cons, and a sample implementation that you can extend.

Here's a list of features that I'd like to see in VS. I'm grouping them by version to show if/when they are ever handled.

Here's a list of features that I'd like to see in C#. I'm grouping them by version to show if/when they are ever handled.

After endless searching for answers to my handler setup questions, I finally decided to write an all-inclusive set of articles about how someone should go about this. If you find any errors or see room for improvement in any way, please let me know - I will make sure to note any contributions in the "Special Thanks" section. This will be my first contribution to this article-set.

If you've been working with .NET for a while, I'm sure you've had the chance to create a collection before. Well, so have I. But, as I dug up old code two or three times, I figured there had to be an easier way to reuse this stuff. So, I figured I'd just make a template.