dotnetcore

All related links: https://www.theurlist.com/autobloggerpost Jekyll is a very popular way to host a static site on GitHub and posting new content is a simple as creating a markdown file and then committing it to the relative repo. GitHub takes care of the rest. See the help pages at GitHub -> Setting up your GitHub Pages site locally with Jekyll This seemed like a great way for me to get started on a blog for some content that was being stored in a CMS. The view we are interested in is updated once a week and is accessible via .NET Standard API. There are a few options for making this happen. I could write a console application...

The options for pushing your .NET Core application to the cloud are not lacking depending on what IDE or editor you have in front of you. Visual Studio has a rich GUI interface with choices to pick pursuant to the architecture of your app - Web, Containers, SQL Server, Registries, etc.; and for years has excelled at delivering a full experience. VS Code offers a great Azure extension pack and in its own fashion delivers an experience to publish your web application directly to an AppService, Container and/or Registry too. If the command line experience is more your "thing", the Azure CLI is available and any resource publish option can be had through the az command. But what if...

The Docker extension for VS Code was recently updated to better support .NET Core applications and the experience is super nice! The extension already has great support for building your containers, pushing images to Docker Hub, Azure Container Registry and tasks such as running a specific image or tagging an image too. However, adding a Dockerfile to an ASP.NET Core application was not updated to support the microsoft/dotnet base images. The Docker extension can be downloaded separately or is also available as a part of the Azure extension pack for VS Code which provides a number of other extensions for working with the many cloud services without leaving the editor. First, I'll start by creating a quick Razor...

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...

In 2016 at the MVP Summit hackathon I put together a .NET Core CLI Tool to search for docs on docs.microsoft.com and it worked well, but there were some shortcomings. It was scoped to the project, and there was no way to install the Nuget package using the command line tools or package manager. <ItemGroup> <DotNetCliToolReference Include="dotnet-doc" Version="1.0.0" /> </ItemGroup> Now with the availability of .NET Core Global tools, see announcement post here, where we can install the Nuget package globally like a node.js package npm install -g <package_name>, I took a few hours to update the project. dotnet install tool -g dotnet-doc Getting Started...