Application Pools in IIS can be somewhat of a mystery. Since they're created for you automatically many times administrators and developers don't give them a second thought.
But when things go wrong with an Application Pool it can get very confusing.
We preach reusability and sometimes strive for it, but it rarely becomes a reality.
A peek at my Virtualization setup that I use to develop software, create courses, and write articles. A detailed step by step, with Debian 9 and VirtualBox.
Recently I found an ORM that I really like: Dapper. It’s small, simple, and fast. It can be useful on even the smallest of projects. Dapper is a simple object mapper for .Net that extends the IDbConnection interface. It contains helpers that execute queries and map results in a very elegant way. The best part is the performance is close enough to plain old SQL that it’s well worth it. It will reduce the amount of code you write as well, by a long shot.
So I started a little project on GitHub of some C# coding guidelines. I want to do this to open up a community driven discussion about guidelines and best practices. I don't want it to be written gospel by me, but rather contributions from other C# coders that we can all learn from.