The long awaited support for .NET Core 3.1 on AWS Lambda has finally been released. My Twitter bot runs on .NET Core 2.1 in a Lambda function and I have been meaning to update it to .NET Core 3.1 since the beginning. So let’s do just that! I’ll be following the steps on the announcement blog post to migrate to 3.1. Project file First up, the TargetFrameowrk in the project file (csproj) needs to be updated, so let’s do that:

I built the website JSON Validate with Blazor some time ago for the purposes of trying out Blazor, and have been updating it upon each release of Blazor since. But, I haven’t updated it in a while, and Blazor 3.2.0 Preview 2 and 3 were just released with some cool features so I thought it was about time to update. Update to 3.2.0 Preview 2 The website is currently on 3.

.NET 5 Preview 1 was recently released and one of the improvements has been in Regex performance. And Although Microsoft have said they will do a deep dive on Regex performance soon (edit: Microsoft’s deep dive), I thought doing some preliminary benchmarks might be a nice way to test out Preview 1. Disclaimer: these are microbenchmarks done outside of a lab, on a small dev machine, so take them with a grain of salt.

Microsoft have released a tool to more easily uninstall old .NET SDKs and Runtime’s from your machine. I use a Mac for my development and it’s always been annoying that you couldn’t easily remove old .NET versions, so I thought I’d give it a try and let you know how it went. Installing the tool Firstly, you need to install the uninstaller… that’s right. Currently the tool is released as a binary on GitHub because they were having problems releasing it as a .

Disclaimer: this is not a scientific study or research. It is probably has lots of bias, so take it with a grain of salt. However, I wrote it up because I think it’s interesting and hopefully you can get something out of it. I recently deployed .NET Bot (on 14th January 2020), a Twitter bot that would retweet .NET related content, as a learning exercise in how to:

GitHub have recently released a preview version of their CLI (Command Line Interface) to enable you to interact with GitHub from your favourite terminal. Although I use VS Code as my code editor, which has built in Git support, I still favour using GitHub desktop for handling all things Git related; repos, branches, commits and creating pull requests. However, it would be create to not have to run two GUI’s and handle everything from within VS Code via the built in terminal.

Please note: ToolGet has been shutdown in favour of the official .NET Tool search experiences from NuGet and .NET CLI. .NET Tools is a feature that was released with .NET Core 2.1 and provides the following functionality according to the docs: A .NET Tool is a special NuGet package that contains a console application. A Tool can be installed on your machine on a default location that is included in the PATH environment variable or on a custom location.