Bundling compiled code together is done in libraries. These can be DLLs (in Windows land) or so files in Unix-like OSs.
This week we look at how to build a class library in .NET Core and how to reference it in a preexisting application.
Over on the Coding Blocks Slack group, Luke Warren had suggested that I write a post about the .NET Standard. Luckily for him, I’d already been planning on writing one. The original release would have been towards the middle of December 2016, but I decided to bring it forward a few weeks. So without further ado… What’s an ado,…
In the final week of October of 2106, Microsoft announced the release of .NET Core 1.1. In this post I go through some of the changes and design decisions behind them.
It’s exciting stuff, if I do say so.
A deep dive into the files which make up the default Hello, World application. These files are created when you issue the “dotnet new” command at the terminal.
NOTE: This was correct a the time of posting, but changes in the SDK have happened since, and the “dotnet new” command no longer works like that.
I take you through the very first steps that you’ll need to master in order to set up a .NET Core development environment on your computer. Including: installing the SDK, installing the (free) Visual Studio Code IDE, and the C# plugin for it.