Those who have been exploring the RC builds might have noticed a slew of updates coming to the dotnet new command in the dotnet command line. One such feature now allows us to create project templates that can be installed from a NuGet package or local folder.
With .NET Core, we get a lot of stuff for free. If you so choose, wiring up your applications (ASP.NET or Console) with things like Dependency Injection, Configuration and Logging is as simple as can be. .NET Core bakes these features into the framework and usage of does not require a trade-off of power or flexibility.
In this post, I will continue with the "budget" theme we explored in "Developing A .NET Core Site In Windows and Deploying It To A Budget Linux Host" and breakdown where and how I host my database, email services, dedicated production VM and dedicated dev shared hosting environment for Pioneer Code.
I would argue that if you're not using profiling often and early in development, you are "doing it wrong". Proper profiling not only offers a means of catching errors and exceptions early in dev, it also allows you to have a forward looking view on some performance issues