So you've just started building .Net Core applications and really starting to gain some traction. You quickly learn how mature and thorough the .Net Core framework is becoming and think "I need to start writing some unit tests for this!". As it turns out, it's super easy and very intuitive, especially for C# developers.
You may have heard the term “code smells” lately, it seems its being talked about frequently again. In this short post I’ll explain what they are, and a few of them you may run across.
I saw an advertisement for dry ice claiming it cools 5 times better than wet ice. Out of curiosity I had to know if this were true, or at the very least see how much better dry ice performs. I thought I’d gather up a Raspberry Pi and some sensors and find out, using some techniques from my Hands on Internet of Things course released recently.
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.
The IIS manager provides a nice way of tracing requests for troubleshooting problems. In this article I'll show you how easy it is to use this tool to find issues that happen instantly when someone makes a request to your server.
The Microsoft vNext team has been working like crazy to make .Net as open platform as possible, and today we're going to try it out.
Up until now the only ASP/C# development I do on my Mac is under a Virtual Machine. I have a couple “bleeding edge” VMs I use for CTP versions of the framework and Visual Studio. But I never truly develop things on the platform and thought I’d give it a try.
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.