Use serverless functions and CDN to speed up API data calls

ASP.NET Core 2.1 added some great features for making external API calls easier to manage when there are network failures, or the service itself might be down. Scott Hanselman has a great series of posts where he has updated to take advantage of these features. Announcement on HttpClientFactory and documentation at docs.microsoft.com Download .NET Core 2.1 Using Polly we can set up a retry policy, stating a number of retries to attempt and at what interval. services.AddHttpClient<MyClient>(). AddTransientHttpErrorPolicy(policyBuilder => policyBuilder.CircuitBreakerAsync( handledEventsAllowedBeforeBreaking: 2, durationOfBreak: TimeSpan.FromMinutes(1) )); As I was reading through the docs and making the changes to the ASP.NET Core workshop, it struck me to push this...


Using global tool "dotnet outdated" to check for the latest NuGet package updates

Just recently the .NET Core June 2018 Update dropped and the ASP.NET Workshop I had just set up for CI/CD build was in need of an update to 2.1.1 (Release Notes). Get the latest 2.1.1 Runtime | 2.1.301 SDK from the downloads page at http://dot.net/ Looking through all of the save-points there are and of course the main /src, the challenge is to know what NuGet packages have changed and what versions are the latest etc., to be updated. That is where a great .NET global tool, dotnet-outdated comes in to play. Read more about dotnet global tools in the docs Install the tool using the .NET CLI - dotnet tool...


Learning DevOps, building the ASP.NET Core Workshop, and keeping it up to date

DevOps is the union of people, process, and products to enable continuous delivery of value to our end users. – Donovan Brown Build Status BackEnd Web API FrontEnd Razor Page App How often have you gone to a GitHub repo and found that the sample code is not up to date with the latest SDK, or doesn't even build? Over the last couple of weeks, I have jumped into updating (again) the ASP.NET Core Workshop the team uses for 1 and 2-day sessions at various conferences to .NET Core 2.1. However, as a part of that, we wanted to make sure that any future changes were checked and didn't just work on my machine. The workshop has a lot...


Why should we care about containers for development

There has probably been more than one time in your development career where you've spent a few hours troubleshooting an issue only to find out it was a dependency or versions issue right? Environments varying from one to next, outdated components and setting up development machines are frustrations we can all do without. Some of these issues we've solved with VMs, but managing the entire machine and underutilizing them for each environment is costly. This is where containers have come to solve many challenges. Why Containers It's no doubt that you have heard the buzz about containers over the last year or longer. If not containers, then some technology, framework, or tooling associated with it; Docker, Kubernetes, microservices are just...


Creating RazorPage apps using the CLI

While I was creating a recent test application with Razor Pages, I found myself clicking the "new file" button in VS Code too many times when I wanted to add a new Page. I really love the .NET CLI and with every release, there seems to be something I discover that has been added to either the core functionality or the templates. Running dotnet new this time around I fell upon the page template... Within your application, run dotnet new page and a new Razor Page is added to to the project. See the -h|--help some items removed for brevity $ dotnet new page -h -n, --name The name for the output being created. If no name is specified, the...