f56648180f
This change is required for RTM stable builds. When stable versions are generated the CalculateTemplateVersions task will fail. For .NET 3.x, installer is partially on arcade. It uses its own versioning model, but the arcade generated versions are actually set (specifically VersionSuffix). So even when stable builds are generated, VersionSuffix is available. It is unused when the aspnetcore template versions are stable. For .NET 5, installer is now fully on arcade versioning, which means VersionSuffix is not set when stable versions are generated. Instead of using installer's version suffix if aspnetcore's template versions are unstable, use the version suffix of the aspnetcore template versions. This subtley affects the installer directory of the templates: If the aspnetcore version is: 5.0.0-rc.1.1234.5 And the installer version is: 5.0.100-rc.1.9999.9 Then: Template install dir before this change: .dotnet\templates\5.0.0-rc.1.9999.9 Template install dir after this change: .dotnet\templates\5.0.0-rc.1.1234.5 Of note: The overall template layout doesn't make a ton of sense. The aspnetcore template version is used for the install directory, but many different templates are put in this directory, including some that have completely different versions. |
||
|---|---|---|
| eng | ||
| resources/images | ||
| src | ||
| test | ||
| TestAssets | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .vsts-ci.yml | ||
| build.cmd | ||
| build.sh | ||
| CODE-OF-CONDUCT.md | ||
| CONTRIBUTING.md | ||
| Directory.Build.props | ||
| Directory.Build.targets | ||
| Downloads2.x.md | ||
| global.json | ||
| LICENSE | ||
| Microsoft.DotNet.Cli.sln | ||
| NuGet.config | ||
| PULL_REQUEST_TEMPLATE | ||
| README.md | ||
| run-build.ps1 | ||
| run-build.sh | ||
| SECURITY.md | ||
| THIRD-PARTY-NOTICES | ||
.NET Core SDK
This repo contains the source code for the cross-platform .NET Core SDK. It aggregates the .NET Toolchain, the .NET Core runtime, the templates, and the .NET Core Windows Desktop runtime. It produces zip, tarballs, and native packages for various supported platforms.
Looking for released versions of the .NET Core tooling?
Download released versions of the .NET Core tools (CLI, MSBuild and the new csproj) at https://dot.net/core.
Found an issue?
You can consult the Documents Index for the CLI repo to find out current issues, see workarounds, and to see how to file new issues.
This project has adopted the code of conduct defined by the Contributor Covenant to clarify expected behavior in our community. For more information, see the .NET Foundation Code of Conduct.
Build status
| All legs |
|---|
Installers and Binaries
You can download the .NET Core SDK as either an installer (MSI, PKG) or a zip (zip, tar.gz). The .NET Core SDK contains both the .NET Core runtime and CLI tools.
Note: Be aware that the following installers are the latest bits. If you want to install the latest released versions, check out the preceding section. With development builds, internal NuGet feeds are necessary for some scenarios (for example, to acquire the runtime pack for self-contained apps). You can use the following NuGet.config to configure these feeds.
Example:
For .NET 5 builds
<configuration>
<packageSources>
<add key="dotnet5" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet5/nuget/v3/index.json" />
</packageSources>
</configuration>
For .NET 3.1 builds
<configuration>
<packageSources>
<add key="dotnet3.1" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet3.1/nuget/v3/index.json" />
</packageSources>
</configuration>
Reference notes:
1: Our Debian packages are put together slightly differently than the other OS specific installers. Instead of combining everything, we have separate component packages that depend on each other. If you're installing the SDK from the .deb file (via dpkg or similar), then you'll need to install the corresponding dependencies first:
.NET Core SDK 2.x downloads can be found here: .NET Core SDK 2.x Installers and Binaries
Questions & Comments
For all feedback, use the Issues on the .NET CLI repository.
License
By downloading the .zip you are agreeing to the terms in the project EULA.