Software engineering is full of patterns and principles to help you get the job done. Sometimes those patterns and principles are defined very abstract and difficult to understand. Let’s talk about SOLID design principles in a 5 part series. Today we’re discussing the Single Responsibility Principle.
Recently I was faced with some difficult decisions regarding employment. I had been experiencing some internal strife and as a result was “open to new opportunities.” While I hadn’t been actively pursuing options I figured that if something came along I’d at least consider it. Eventually some opportunities interesting enough to pique my interest did hit so I began the process. Nearing the end of my “openness” some external events occurred that set up an interesting situation. Ultimately I was faced with a decision that required me to understand myself and work at finding my motivations.
Breathing new life into a “legacy” ASP.NET website is a way you can help slowly transition the site towards ASP.NET Core. One way you might accomplish that is by referencing .NET Standard libraries. Everything seems fine and dandy until you attempt a publish operation. Generally you might not notice these until running msbuild from command-line–such as in a CI environment, batch deploy script, or otherwise. Let’s talk about one major msbuild error you’ll encounter while publishing your ASP.NET MVC application that references a .NET standard library. We’ll also talk about some other errors that might arise in the process.