NetCoreMvcSamples - Dutch Treat

What is "Dutch Treat"?

Dutch Treat is a sample ASPNetCore2.0 Project based on a Pluralsight course by Shawn Wildermuth.

Branch/Project History

1. feature/htmlCssBasics HTML and CSS foundation. Naive styling with limited CSS. No jQuery, bootstrap, or client side framework.
2. feature/javascriptBasics Adding jQuery and Bootstrap as dependencies and manipulate page elements using both toolsets.
3. feature/usingMvc Implementing basic MVC6 routing, controllers, Razor Layout and Include, and a mail service.
4. feature/usingBootstrap Adding Twitter Bootstrap and jQuery capability to the project to style page elements and bootstrappify the layout.
5. feature/addingEfCore First look at implementing Entity Framework Core with MSSQL Server localdb. Adds entities, migrations, and a repository pattern that is used by a new controller.
6. feature/AspnetMvcApi Here we've added controllers with RESTful verbs only, and no views. These controllers act as data access APIs for performing CRUD operations on our data.
7. feature/aspnetCoreIdentity Adding authentication and authorization to our StoreUser. Enforce through both a cookie scheme for the site and a JWT creation endpoint to obtain a valid token for API calls.
8. feature/typescriptIntro Adding typescript config and a few basic .ts files to play around with.
9. feature/startingAngular Getting @angular into the project. Barely scratches the surface of using the outer appcomponent app container and getting it onto our shop page. This is followed by creating a small component for displaying the list of products in the shop and using markup to get data from the typescript class.
10. feature/servicesWithAngular Implemented a dataService to centralize the data store for the client app. Also provides a launch pad for interacting with the server through our APIs via the HTTP stack. Added summary objects for orders and used mapreduce to summarize data from our classes on the page.
11. feature/routingWithAngular Using angular routes to allow us to navigate around our app to different components. Still within our shop URL, we are navigating around our various app components by way of router-outlet. We also used our token to log in and authorize a new order to be placed.
12. feature/deployment Add build steps to our project and configure gulp to minify our javascript. Now we are ready for production. Quickly change and initialize the dev DB to use sqlite. In practice we would probably want to test with the same DB engine that we are using in production to reduce variables when debugging.