In this episode, we'll explore how to hook up Application Insights to your ASP.NET Core application using the really excellent Serilog.
Serilog - structured logging for .NET
Seq - structured log searching
Should we be checking in NuGet packages? Do we want to ensure that we can reliably recreate builds at a later date or do package managers handle all of that for use? In this episode, we try and get to the bottom of this quandary.
Paket package manager: https://fsprojects.github.io/Paket/
Yarn packages manager: https://yarnpkg.com/en/
NPM5: http://blog.npmjs.org/post/161081169345/v500
Manually deploying NuGet packages to nuget.org can be a bit of a painful process. Fortunately, many build systems provide the ability to automate NuGet package deployment . In today's episode, Monster Dave explores deploying NuGet package using AppVeyor
Previous Episodes:
Hosted ASP.NET Core Builds with AppVeyor
Continuous Deployment with AppVeyor
There are countless front-end workflows. In what we're hoping will be the first of a series of episodes on workflows we talk with noted front-end guru and JavaScript master David Wesst (https://blog.davidwesst.com/). JavaScript or TypeScript? Gulp or Grunt? Hear what one expert thinks is the best combination.
If you happen to head over to https://www.nuget.org/packages and look at which package has been downloaded the most there is a clear winner: JSON.net. It is in everything, every where. JSON is so wildly ubiquitous that I play a little game with myself when I start a new project: how long can I go before I need to serialize or deserialize JSON and need to pull in JSON.net. I rarely last more than a couple of hours.
But it turns out that there is a lot more that JSON.net can do.
Adding deployment steps to your build pipeline is a lot easier than it used to be. In today's episode, Monster Dave explores deployments and environment management using the AppVeyor hosted build service.
Previous Episode: Hosted ASP.NET Core Builds with AppVeyor
A continuous integration (CI) build is a helpful tool for any software project. In today's episode, Monster Dave explores the AppVeyor hosted build service and shows just how easy it is to setup a CI build for your ASP.NET Core project.
In our last episode we set up a Docker container using Windows Containers, in this episode we'll talk a bit about messaging and then send a message using RabbitMQ.
References:
ASP.NET Monsters blog on RabbitMQ
This blog is part of a series exploring RabbitMQ and MassTransit. Previous episodes are available at
- Creating a RabbitMQ Container
- Getting Started with RabbitMQ in ASP.NET
- MassTransit on RabbitMQ in ASP.NET Core
In the last episode I did a lot of handwaving over the mess I made of configuration. There were hard coded values all over the place. In this article we’ll clear up some of the mess we made.
Docker is now fully sported on Windows 10. In this episode we'll see what it takes to avoid installing RabbitMQ locally and, instead, use a Windows container. Keeping RabbitMQ in a container allows standing up a cluster on one physical machine, greater ability to experiment and a high degree of isolation. In the future we expect that a great deal of local development will leverage containers.