When developing an ASP.net application, it can be very useful to be able to quickly set up the project in your local IIS server so you can build it and start using it.
When using TeamCity to run daily builds for things like unit test coverage, duplicate code, security auditing, which can be time consuming running as part of every commit, it is handy to be able to see which date they were run.
A list of essentials tools when setting up a new machine for software development.
Psake is a great build system for automating your .Net builds on Windows. To save time when using it and to make it a simple command to run the build, I like to place a batch file in the root of the code repository to allow you to download and execute Psake without having to check in any binaries.
MargieBot is a simple to use .Net framework for making your own bots for Slack. To start up a bot and connect it to Slack, all it takes is:
When writing a simple HTTP handler in .Net, the framework provides support for replacing the default HTTP Handler Factory with your own factory which provides support for dependency injection.
When creating a new ASP.Net MVC project, by default you will end up with a number of extra HTTP headers in your responses which can safely be removed.
When starting a new .Net project, I like to place a nuget.config in the solution root folder with a number of default settings in place. This is to ensure a number of good behaviours for NuGet.
Castle Windsor has a great add on called the WCF Integration Facility which allows you to get all of the benefits of DI/IoC when working with WCF services.