Ultimate pipeline for NuGet packages
Here I explain how to create the ultimate pipeline for NuGet packages with Azure DevOps as the end of my previous posts. Click to see it
All technologies, only pure source code
.NET (dotnet) is a developer platform made up of tools, programming languages, and libraries for building many different types of applications.
So, there are various implementations of .NET (dotnet). Each implementation allows .NET code to execute in different places—Linux, macOS, Windows, iOS, Android, and many more. This framework has two main versions:
Then, Xamarin/Mono is a .NET (dotnet) implementation for running apps on all the major mobile operating systems, including iOS and Android.
The .NET Standard is a formal specification of the APIs that are common across .NET implementations. This allows the same code and libraries to run on different implementations.
Therefore, the two major components of .NET (dotnet) Framework are the Common Language Runtime and the .NET Framework Class Library.
Summarize, .NET (dotnet) applications are written in the C#, F#, or Visual Basic programming language. Code is compiled into a language-agnostic Common Intermediate Language (CIL). Compiled code is stored in assemblies—files with a .dll or .exe file extension.
At the end, when an app runs, the CLR takes the assembly and uses a just-in-time compiler (JIT) to turn it into machine code that can execute on the specific architecture of the computer it is running on.
Here I explain how to create the ultimate pipeline for NuGet packages with Azure DevOps as the end of my previous posts. Click to see it
We have just released a lot of functions for .NET5 in a NuGet package that you can download for free. Contains functions for everyday work
Today we are going to create our own NuGet package, publish it to Azure DevOps, and then consume it in our application.