SOLID in C#: The Single Responsibility Principle

What Is This Principle? The Single Responsibility Principle [http://en.wikipedia.org/wiki/Single_responsibility_principle] (SRP) states that any class must have one, and only one, reason to change. If a class has more than one reason to change, it should be refactored. Benefits The primary benefit the Single-Responsibility

Doing it Right vs Getting it Done

> The first 90% of the code accounts for the first 90% of the development time. The remaining 10% of the code accounts for the other 90% of the development time. > - The 90-90 Rule [http://en.wikipedia.org/wiki/Ninety-ninety_rule], proposed by Tom Cargill There's a classic, constant pull

ActionResult in ASP.NET MVC

See the different ActionResults and learn about when to use each of them, including ViewResult and JsonResult. Sample project included!

Are users trying to make developers angry?

Have you ever felt like users are intentionally trying to piss you off? This feeling has happened to me more than once. It isn't a rare occurance for my team to get angry emails from our users saying something doesn't work, only for us to point out something simple that

Bundling and Minification - ASP.NET MVC Demystified

Let's learn how to enable or disable two optimizations provided by ASP.NET MVC: bundling and minification.