Asp.Net Core 2
In this series we will be focusing on all things Asp.Net Core 2.
We will start with one or more articles that can be used to get up and running using Asp.Net Core 2 as quickly as possible. The subsequent articles will be more in depth and will
be based on both the documentation and additional components that will add functionality to the core product.
#5 Emailing Exceptions
In this article we will create both a template and model that we can use to generate an email from an exception. With
that in place we will then create a middleware that we can use to send an email automatically if our application
encounters an unhandled exception. And of course to do this the last step will be to add our new middleware to the
pipeline within our Startup class.
#4 Sending Email Using Mailkit
In this article we will create the ability to send emails from our web application using the Mailkit nuget package. In
addition to sending basic emails our message service will also be able to deal with the cases when we want to send along
attachments as well.
#3 View Location Expander and View Renderer
In this article we will expand the locations that the razor view engine will search to find razor views and we will
create a razor view renderer that we can inject into our controllers and pages. We are doing this for a few different
reasons but the two we will be exploring in just a little while is sending emails and indexing the content of our
application for full text searching.
#2 Upgrade to Version 2.1
In this article we take the steps to upgrade our project from version 2.0 to version 2.1. These changes
range from setting and enforcing the use of https for both our development environment as well as
production to moving our common layout page to a different location. At the end we will also create a new
npm script command to make it easier to start up our development server.
#1 Quick Start
In this article we will begin by creating a new project using the web application template provided in
Visual Studio. Once the project is created we
will remove the unnecessary parts that are included in the template, modify the existing shared layout and
home pages and finally set our project up to use the hot module replacement capabilities of webpack.