You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rolf Bjarne Kvinge edited this page Nov 11, 2025
·
4 revisions
Use a daily/prerelease version
Find the package for the version you want to try.
Every commit will create packages, which means that you can try whichever commit you want (assuming the commit in question actually builds, and that enough time has passed for build to complete - it usually takes 8-12 hours).
Scroll down until you see a comment that says "Packages generated". Expand the "View packages" text, and download the Microsoft.<platform>.Bundle.<version>.pkg (notarized) link.
If the commit in question doesn't have packages (for whatever reason), you can always look at the parent commit.
If you want a commit from the main branch, you can go here: commits in main, start at the top, and check every commit to see if it has packages.
Identify the .NET version this package was built with.
This might not be required, if you have a close .NET version installed already it might work, but we recommend using the exact same version. There are often breaking changes that require a matching .NET install.
Go to the eng/Version.Details.xml file for the commit in question, and get the Microsoft.Dotnet.Sdk.Internal version.
Download the package for the .NET version in question and install it. This is a bit complicated, but it usually works to get the link for a similar version, and change just change the version in the URL.
The --skip-manifest-update argument is important, otherwise .NET will update the manifests to the official ones, and you'll end up installing the official versions.
Add a global.json
Add a global.json with the following content:
{
"sdk": {
"version": "<.NET version from step #2>"
}
}