The ASP.NET Core 3.1 workshop teaches you how to build your first application using a microservice architecture, view models, and razor pages.

In this first module, Jeff talks about the benefits of .NET Core, ASP.NET Core, and how you can get started on any operating system with any editor. We build our first API and configure it as an OpenAPI endpoint with Swashbuckle.

00:04:00 – Introduction to the project and GitHub repository with the samples
00:09:06 – Get .NET Core, how to download and get started
00:34:13 – Discussion of the project and data model
00:44:05 – Building our first project
00:59:35 – Starting database interactions with Entity Framework Core
01:43:30 – Introducing RESTful APIs using Controllers
02:00:24 – Adding OpenAPI / Swagger capabilities with Swashbuckle

00:14:55 – Are Razor Pages more encouraged than MVC?
00:16:32 – Can you review each of the .NET Core project templates and the advantages / disadvantages of each?
00:54:52 – What about the [Key] attribute on the Id field? Is it needed?
00:56:40 – When should you choose .NET Framework vs. .NET Core?
01:02:03 – Is there a way to list what database packages are available?
01:24:37 – Is database context transient or scoped lifetime?
01:33:53 – Can we execute dotnet commands inside Visual Studio using the console there, or do we have to use the terminal in Windows?
01:36:24 – What are the benefits of using .NET for Web Applications as opposed to PHP or Node?
01:38:20 – Should database migration be part of the deployment process when deploying to production?
01:39:15 – For a ‘compiled’ application ready to deploy to a server, do I need to deploy the deployment tools as well in order to run migrations on the production server?
01:53:01 – Is there a change in the way Silicon Valley developers perceive C# and .NET?

Get .NET Core:
Get Visual Studio Code:
Music played is “Music to Code By”:
Originally broadcast live on