Configuring ASP.NET Core, webpack, and hot module replacement (hmr) for fast TypeScript development
This project setup supports browser live-reloading changes to TypeScript files while you develop in ASP.NET Core
Recently, I spent a weekend banging my head against the wall as I tried to figure out how to upgrade a personal project to webpack 4, TypeScript 2.9, and React (used to be AngularJS 1.6). I finally got it all working together – and even got hot module replacement (hmr) working. TL;DR? Checkout the code here: https://github.com/natemcmaster/aspnetcore-webpack-hmr-demo
Enabling code signing with NuGet, Azure Key Vault, and AppVeyor
About 4 weeks ago, I decided to code sign the NuGet packages from my personal open-source projects. I finally succeeded this weekend. When I started, I figured it couldn’t be that hard. In the end, it really isn’t, but it took hours of research to figure out how to tie it all together. In this post, I’ll share the technical details of what it took to enable code signing using Azure Key Vault, AppVeyor, and NuGet for one of my .NET Core projects.
dotnet watch 2.1
It's now a built-in command and it works inside Docker.
.NET Core 2.1 RC1
was released this week.
This is the first supported version of the .NET Core CLI which ships
dotnet watch as a built-in command.
In addition to changing how this tool ships, dotnet-watch 2.1 has a few improvements that make it
the best version yet.
.NET Core 2.1 Global Tools
Getting started with creating a .NET Core global tool package. Also, a peek under the hood.
.NET Core 2.1 RC1 was released this week. This is the first supported version of the .NET Core CLI which includes a feature called “.NET Core Global Tools”. This feature provides a simple way to create and share cross-platform console tools. In this post, I’ll go over some of the basics, and then walk though what is going on under the hood. You will need to download .NET Core 2.1 to use this to try this on your own.