About .NET
How to use FAKE to automatically set version numbers based on your
Git history.
For Fake.StaticGen,
I wanted to have a semi-automated way of determining the version number
for each release. Inspired by Nerdbank.GitVersioning,
I liked the idea of having a unique version for every commit, but I …
.NET Core versioning is a mess. There are lots and lots and lots of
version numbers, from runtime to SDK, from Visual Studio to languages
and of course .NET Standard. So what SDK corresponds to which runtime
again? I know there some sort of a system, but it differs per …
To display version information about .NET Core on versionsof.net,
I had to decode the releases.json
files in the dotnet/core repo. Not a big
problem, you’d think. These are just JSON files, how hard can it be?
That’s fair, but the schema, nor the data of …
.NET Core versioning is a mess. There are lots and lots and lots of
version numbers, from runtime to SDK, from Visual Studio to languages
and of course .NET Standard. So what SDK corresponds to which runtime
again? I know there some sort of a system, but it differs per …
On what I think are the biggest problems with education about .NET,
and how I would do things different if I were to create a tutorial on C# today.
I was listening to a .NET Rocks! episode with Ian Cooper
about starting a .NET Renaissance, analogous to the Java Renaissance …
How to set your package versions dynamically without creating an
AssemblyInfo.cs file.
After the debacle with project.json and .xproj, Microsoft settled on
a simpler, more modern version of the old .csproj project system with
Visual Studio 2017. One of the changes advanced users will notice when
creating a …