Posts


Other Views: By Month | By Category | By Tag Cloud


ASP.NET Core - AutoMapper - Easily Convert One Object to Another

Mapping code is boring. Testing mapping code is even more boring.

AutoMapper is a simple library built to map one object to another and takes out all of the fuss of mapping one object to another.

In this post, we will create a sample ASP.NET Core API project, install and wire up AutoMapper, and update the sample Weather Forecast Controller to return a view model that was converted from our concrete object to a view model object.

Read More


VS Code - Favorite Extension - Github Pull Request and Issues

In this series, we are looking at some of my favorite VS Code extensions.

Extensions in VS Code are invaluable to speed up your work and make you more productive.

In this post, we will look at the GitHub Pull Request and Issues extension that allows you to stay where you are writing your code and manage your GitHub pull requests and issues right from VS Code

Read More


VS Code - Favorite Extension - Angular 2 Switcher

In this series, we are looking at some of my favorite VS Code extensions.

Extensions in VS Code are invaluable to speed up your work and make you more productive.

In this post, we will look at Angular2 Switcher which provides shortcuts to switch between the TypeScript, StyleSheet, Spec, and Html files for your Angular files.

Read More


VS Code - Favorite Extension - markdownlint

In this series, we are taking a look at some of my favorite VS Code extensions.

Extension in VS Code are invaluable to speed up your work and make you more productive.

In this post, we are going to look at Markdown Lint which provides Markdown/CommonMark linting and style checking for markdown files.

Markdownlint has make my markdown output much more predictable and easier for others dev to follow.

Read More


VS Code - Favorite Extension - Path Intellisense

In this series, we are taking a look at some of my favorite VS Code extensions.

Extension in VS Code are invaluable to speed up your work and make you more productive.

In this post, we are going to look at Path Intellisense which autocompletes file names.

Read More


VS Code - Favorite Extension - FoldPlus

In this series, we are taking a look at some of my favorite VS Code extensions.

Extension in VS Code are invaluable to speed up your work and make you more productive.

In this post, we are going to look at Fold Plus which enables you to quickly expand or collapse sections within a file.

Read More


VS Code Favorite Extension Series - Add Only

Extension in VS Code are invaluable to speed up your work and make you more productive. In this series, we are taking a look at some of my favorite VS Code extensions.

In this post, we are going to look at Add Only to quickly add or remove a .Only to your tests.

Read More


ASP.NET - Health Checks - Generic Endpoint

In the previous post in the series, we have implemented our health checks that return a json response and allow us to selectively run the health checks based on tags.

In this post, we are going to build on the previous post and update our endpoint mappings to use a generic endpoint builder so that we only have our filters and json response code in a single place.

Read More


ASP.NET - Selectively Run Health Checks

In part 1 we create our basic ASP.NET Core health check and then in part 2 we changed from plain text “Healthy” or “Unhealthy” to a json response that let us know the stauts of each health check.

In our previous post, we have only have a single health check so it has been ok to have all health checks run when we hit our health check endpoint. However, if we had multiple health checks we are going to want to be able to run them by themselves as well as run the whole suite.

In this post, we will are going to add the ability to selectively run our health checks and create endpoints that will run either a set of health checks or all of the health checks.

Read More


ASP.NET - Health Checks - Generate Better Response Than Just Text

In our previous post, we added a simple health check to our ASP.NET Core application. Although we only added a single health check, you can add multiple health checks and have multiple run as once. Regardless if you run a single or multiple health checks, the implementation out of the box, just returns a “Healthy” or “Unhealthy” string, which is not overall helpful to know which component actually failed.

In this post, we are going to update our health check response to return a json record that will let us know the status of each health check that is run as well as the overall health status of the application.

{
    "status": "Healthy",
    "duration": "00:00:00.0066738",
    "info":
    [
        {
        "key": "ExampleHealthCheckAsync",
        "description": "Health Msg Here.",
        "duration": "00:00:00.0010113",
        "status": "Healthy",
        "data": {}
        }
    ]
}

Read More