This document provides the steps necessary to consume a latest development build of .NET runtime and SDK. Example below is for 8.0 but similar steps should work for other versions as well.
If you are only looking to get fixes for an individual NuGet package, and don't need a preview version of the entire runtime, you can add the development package feed to your NuGet.config file. The easiest way to do this is by using the dotnet CLI:
(Recommended) Create a local NuGet.Config file for your solution, if don't already have one. Using a local NuGet.Config file will enable the development feed as a package source for projects in the current directory only.
dotnet new nugetconfig
Next, add the package source to NuGet.Config with the dotnet nuget add source command:
dotnet nuget add source -n dotnet8 https://dnceng.pkgs.visualstudio.com/public/_packaging/dotnet8/nuget/v3/index.json
Then, you will be able to add the latest prerelease version of the desired package to your project.
Example: To add version 8.0-preview.5.22226.4 of the System.Data.OleDb package, use the dotnet add package command:
dotnet add package System.Data.OleDb -v 8.0-preview.5.22226.4
To use daily builds of the entire runtime, follow the steps given in the rest of this document instead.
If you're using private Azure DevOps feeds for your projects, you might need to add the preview feed through the Azure-specific feed URI format, which is azure-feed://organization/optionalProject/feed@view. In this case, you can add the .NET development package feed as follows:
azure-feed://dnceng/public/dotnet8@Local
-
Acquire the latest development .NET SDK by downloading and extracting a zip/tarball or using an installer from the installers and binaries table in dotnet/installer (for example, https://aka.ms/dotnet/8.0/daily/dotnet-sdk-win-x64.zip).
-
If you are using a local copy of the dotnet CLI, take care that when you type
dotnetyou do not inadvertently pick up a different copy that you may have in your path. On Windows, for example, if you use a Command Prompt, a global copy may be in the path, so use the fully qualified path to your localdotnet(e.g.C:\dotnet\dotnet.exe). If you receive an error "error NETSDK1045: The current .NET SDK does not support targeting .NET 8.0." then you may be executing an olderdotnet.
After setting up dotnet you can verify you are using the dogfooding version by executing dotnet --info. Here is an example output at the time of writing:
>dotnet --info
.NET SDK:
Version: 8.0.100-preview.5.22226.4
Commit: fc127ac5a4
Runtime Environment:
OS Name: Windows
OS Version: 10.0.22616
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\8.0.100-preview.5.22226.4\
global.json file:
Not found
Host:
Version: 8.0.0-preview.5.22224.3
Architecture: x64
Commit: 47d9c43ab1
.NET SDKs installed:
8.0.100-preview.5.22226.4 [C:\Program Files\dotnet\sdk]
.NET runtimes installed:
Microsoft.NETCore.App 8.0.0-preview.5.22224.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Download .NET:
https://aka.ms/dotnet-download
Learn about .NET Runtimes and SDKs:
https://aka.ms/dotnet/runtimes-sdk-info
- Our daily builds are uploaded to development feed, not NuGet - so ensure the development feed is in your nuget configuration in case you need other packages that aren't included in the download. For example, on Windows you could edit
%userprofile%\appdata\roaming\nuget\nuget.configor on Linux edit~/.nuget/NuGet/NuGet.Configto add these lines:
<packageSources>
<add key="dotnet8" value="https://dnceng.pkgs.visualstudio.com/public/_packaging/dotnet8/nuget/v3/index.json" />
...
</packageSources>(Documentation for configuring feeds is here.)
-
Create a new project
- Create a new folder for your app and change to that folder
- Create project file by running
dotnet new console
-
Restore packages so that you're ready to play:
$ dotnet restore
$ dotnet run
Rinse and repeat!
When using the above instructions, your application will run against the same .NET runtime that comes with the SDK. That works fine to get up and running quickly. However, there are times when you need to use a daily build of Microsoft.NETCore.App which hasn't made its way into the SDK yet. To enable this, there are two options you can take.
This is the default case for applications - running against an installed .NET runtime.
- You still need to install the prerequisite .NET SDK from above.
- Optionally, install the specific .NET runtime you require globally or download get the latest one available from the daily build table
- Modify your .csproj to reference the daily build of Microsoft.NETCore.App
<PropertyGroup>
<OutputType>Exe</OutputType>
<!-- Ensure that the target framework is correct e.g. 'net8.0' -->
<TargetFramework>net8.0</TargetFramework>
<!-- modify version in this line with one reported by `dotnet --info` under ".NET runtimes installed" -> Microsoft.NETCore.App -->
<RuntimeFrameworkVersion>8.0.0-preview.5.22224.3</RuntimeFrameworkVersion>
</PropertyGroup>$ dotnet restore
$ dotnet run
In this case, the .NET runtime will be published along with your application.
- You still need to install the prerequisite .NET SDK from above.
- Modify your .csproj to reference the daily build of Microsoft.NETCore.App and make it self-contained by adding a RuntimeIdentifier (RID).
<PropertyGroup>
<OutputType>Exe</OutputType>
<!-- Ensure that the target framework is correct e.g. 'net8.0' -->
<TargetFramework>net8.0</TargetFramework>
<!-- modify build in this line with version reported by `dotnet --info` as above under ".NET runtimes installed" -> Microsoft.NETCore.App -->
<!-- moreover, this can be any valid Microsoft.NETCore.App package version from https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet8/nuget/v3/index.json -->
<RuntimeFrameworkVersion>8.0.0-preview.5.22224.3</RuntimeFrameworkVersion>
<RuntimeIdentifier>win-x64</RuntimeIdentifier> <!-- RID to make it self-contained -->
</PropertyGroup>$ dotnet restore
$ dotnet publish
$ bin\Debug\net8.0\win-x64\publish\App.exe
Note: Our Linux packages (.deb and .rpm) are put together slightly differently than the Windows and Mac specific installers. Instead of combining everything, we have separate component packages that depend on each other. If you're installing these directly from the installer files (via dpkg or similar), then you'll need to install them in the order presented above.