* Add an explicit dependency on the 6.0 project templates
These ship incrementally, so it's important to keep the dependencies separate from other templating dependencies
* Use the shared framework VS redist package version to find the windows desktop blobs
Using the targeting pack version is incorrect
After https://github.com/dotnet/installer/pull/11843, post build signing started failing, failing to find one of the input wixobj files. The wixobj was not included in the wixpack. This is because the installer repo uses custom scripts to generate MSIs, rather than the arcade tasks (which would handle adding this transparently), so the input files need to be added explicitly.
* Tweaks for RTM stable building and servicing
- When building from source offline in a stable configuration, the shared frameworks versions will match the directory from which the runtime archives are located in, both stable. This is in contrast to when not building from source, in which the runtime archives will appear in non-stable directories.
- The targeting pack versions should not be assumed to always match the runtime framework versions, and the blob directories containing them are the same. Add new dependencies so that we can track where the targeting pack directory is over time.
- PGO archives coming from runtime are always built non-stable. This means the download location needs to be tweaks, and crossgen calls need to look for shared framework binaries in the non-stable locations.
- For source-build, the templating should move to a new non-stable dependency. This is used to determine the version of the source build intermediate package.
* Generate the full nuget version in the source build tarball job.
The source build tarball job needs the full nuget version so that it can publish the blob to the right location (`Sdk/<full version>/source-<stable version>.zip). This involves being able to call the GenerateFullNuGetVersion target and the targets it depends on.
[release/6.0.1xx] Update dependencies from dotnet/sdk
- Coherency Updates:
- Microsoft.WindowsDesktop.App.Ref: from 6.0.0-rc.2.21423.1 to 6.0.0-rc.2.21427.2 (parent: Microsoft.NET.Sdk)
- VS.Redist.Common.WindowsDesktop.SharedFramework.x64.6.0: from 6.0.0-rc.2.21423.1 to 6.0.0-rc.2.21427.2 (parent: Microsoft.NET.Sdk)
- Microsoft.NETCore.App.Ref: from 6.0.0-rc.2.21423.6 to 6.0.0-rc.2.21427.5 (parent: Microsoft.NET.Sdk)
- Microsoft.NETCore.App.Runtime.win-x64: from 6.0.0-rc.2.21423.6 to 6.0.0-rc.2.21427.5 (parent: Microsoft.NET.Sdk)
- Microsoft.NETCore.App.Host.win-x64: from 6.0.0-rc.2.21423.6 to 6.0.0-rc.2.21427.5 (parent: Microsoft.NET.Sdk)
- Microsoft.NETCore.DotNetHostResolver: from 6.0.0-rc.2.21423.6 to 6.0.0-rc.2.21427.5 (parent: Microsoft.NET.Sdk)
- Microsoft.NETCore.Platforms: from 6.0.0-rc.2.21423.6 to 6.0.0-rc.2.21427.5 (parent: Microsoft.NET.Sdk)
- Microsoft.AspNetCore.App.Ref: from 6.0.0-rc.2.21420.26 to 6.0.0-rc.2.21427.4 (parent: Microsoft.NET.Sdk)
- Microsoft.AspNetCore.App.Ref.Internal: from 6.0.0-rc.2.21420.26 to 6.0.0-rc.2.21427.4 (parent: Microsoft.NET.Sdk)
- Microsoft.AspNetCore.App.Runtime.win-x64: from 6.0.0-rc.2.21420.26 to 6.0.0-rc.2.21427.4 (parent: Microsoft.NET.Sdk)
- VS.Redist.Common.AspNetCore.SharedFramework.x64.6.0: from 6.0.0-rc.2.21420.26 to 6.0.0-rc.2.21427.4 (parent: Microsoft.NET.Sdk)
- dotnet-dev-certs: from 6.0.0-rc.2.21420.26 to 6.0.0-rc.2.21427.4 (parent: Microsoft.NET.Sdk)
- dotnet-user-secrets: from 6.0.0-rc.2.21420.26 to 6.0.0-rc.2.21427.4 (parent: Microsoft.NET.Sdk)
- Microsoft.DotNet.Common.ItemTemplates: from 6.0.100-rc.2.21423.5 to 6.0.100-rc.2.21426.9 (parent: Microsoft.NET.Sdk)
- Microsoft.WindowsDesktop.App.Runtime.win-x64: from 6.0.0-rc.2.21423.1 to 6.0.0-rc.2.21427.2 (parent: Microsoft.NET.Sdk)
- Microsoft.Dotnet.WinForms.ProjectTemplates: from 6.0.0-rc.2.21423.3 to 6.0.0-rc.2.21427.1 (parent: Microsoft.WindowsDesktop.App.Runtime.win-x64)
- Microsoft.WindowsDesktop.App.Runtime.win-x64: from 6.0.0-rc.2.21423.1 to 6.0.0-rc.2.21427.2 (parent: Microsoft.NET.Sdk)
- Microsoft.DotNet.Wpf.ProjectTemplates: from 6.0.0-rc.2.21423.3 to 6.0.0-rc.2.21427.2 (parent: Microsoft.WindowsDesktop.App.Runtime.win-x64)
- Microsoft.FSharp.Compiler: from 12.0.0-beta.21418.3 to 12.0.0-beta.21426.5 (parent: Microsoft.NET.Sdk)
- Microsoft.SourceBuild.Intermediate.fsharp: from 5.0.3-beta.21418.3 to 5.0.3-beta.21426.5 (parent: Microsoft.NET.Sdk)
- Microsoft.Net.Compilers.Toolset: from 4.0.0-4.21420.19 to 4.0.0-4.21427.2 (parent: Microsoft.NET.Sdk)
- Microsoft.Build: from 17.0.0-preview-21423-05 to 17.0.0-preview-21427-02 (parent: Microsoft.NET.Sdk)
- VS.Redist.Common.NetCore.SharedFramework.x64.6.0: from 6.0.0-rc.2.21423.6 to 6.0.0-rc.2.21427.5 (parent: Microsoft.NET.Sdk)
- Microsoft.NET.Workload.Emscripten.Manifest-6.0.100: from 6.0.0-rc.1.21419.1 to 6.0.0-rc.2.21425.6 (parent: VS.Redist.Common.NetCore.SharedFramework.x64.6.0)
- Update stage0
- Update package name for Microsoft.DotNet.Web.ItemTemplates
React to this commit in aspnetcore that updated the package name to be suffixed with the Major.Minor of the current release: 43f52607fa
[release/6.0.1xx-rc1] Update dependencies from dotnet/sdk
- Coherency Updates:
- Microsoft.NETCore.App.Ref: from 6.0.0-rc.1.21425.15 to 6.0.0-rc.1.21426.17 (parent: Microsoft.NET.Sdk)
- Microsoft.NETCore.App.Runtime.win-x64: from 6.0.0-rc.1.21425.15 to 6.0.0-rc.1.21426.17 (parent: Microsoft.NET.Sdk)
- Microsoft.NETCore.App.Host.win-x64: from 6.0.0-rc.1.21425.15 to 6.0.0-rc.1.21426.17 (parent: Microsoft.NET.Sdk)
- Microsoft.NETCore.DotNetHostResolver: from 6.0.0-rc.1.21425.15 to 6.0.0-rc.1.21426.17 (parent: Microsoft.NET.Sdk)
- Microsoft.NETCore.Platforms: from 6.0.0-rc.1.21425.15 to 6.0.0-rc.1.21426.17 (parent: Microsoft.NET.Sdk)
- Microsoft.AspNetCore.App.Ref: from 6.0.0-rc.1.21425.34 to 6.0.0-rc.1.21426.34 (parent: Microsoft.NET.Sdk)
- Microsoft.AspNetCore.App.Ref.Internal: from 6.0.0-rc.1.21425.34 to 6.0.0-rc.1.21426.34 (parent: Microsoft.NET.Sdk)
- Microsoft.AspNetCore.App.Runtime.win-x64: from 6.0.0-rc.1.21425.34 to 6.0.0-rc.1.21426.34 (parent: Microsoft.NET.Sdk)
- VS.Redist.Common.AspNetCore.SharedFramework.x64.6.0: from 6.0.0-rc.1.21425.34 to 6.0.0-rc.1.21426.34 (parent: Microsoft.NET.Sdk)
- dotnet-dev-certs: from 6.0.0-rc.1.21425.34 to 6.0.0-rc.1.21426.34 (parent: Microsoft.NET.Sdk)
- dotnet-user-secrets: from 6.0.0-rc.1.21425.34 to 6.0.0-rc.1.21426.34 (parent: Microsoft.NET.Sdk)
- Microsoft.DotNet.Common.ItemTemplates: from 6.0.100-rc.1.21426.4 to 6.0.100-rc.1.21426.10 (parent: Microsoft.NET.Sdk)
- Microsoft.FSharp.Compiler: from 12.0.0-beta.21426.1 to 12.0.0-beta.21426.5 (parent: Microsoft.NET.Sdk)
- Microsoft.SourceBuild.Intermediate.fsharp: from 5.0.3-beta.21426.1 to 5.0.3-beta.21426.5 (parent: Microsoft.NET.Sdk)
- Microsoft.Net.Compilers.Toolset: from 4.0.0-4.21426.10 to 4.0.0-4.21426.21 (parent: Microsoft.NET.Sdk)
- VS.Redist.Common.NetCore.SharedFramework.x64.6.0: from 6.0.0-rc.1.21425.15 to 6.0.0-rc.1.21426.17 (parent: Microsoft.NET.Sdk)
- Update package name for Microsoft.DotNet.Web.ItemTemplates
React to this commit in aspnetcore that updated the package name to be suffixed with the Major.Minor of the current release: 43f52607fa
* [ArPow] Add runtime repo to tarball (#11506)
* Add runtime repo / update runtime project
* Update runtime-portable logs and properties
* Create runtime-portable git-info
* Fix unpack of IntermediatePackages
* Re-enable references to runtime
* Pass TargetRid and NonPortable to runtime build
* Only build allconfigurations in non-portable build
* Add SDK patch to disable new CA warning
* Increase built tarball timeout
* Update prebuilt version
* [ArPow] Add installer repo to tarball (#11483)
* Ignore failure in no-network case
Co-authored-by: Dan Seefeldt <dseefeld@microsoft.com>
Co-authored-by: Michael Simons <msimons@microsoft.com>
Co-authored-by: Matt Galbraith <mattgal@microsoft.com>
Add a 50 bundled version as not all three were changing at once. Modify the code to use the 31 and 21 versions. This way, we only ever have to update one set of numbers each month rather than 3.
- Cherry pick the internal runtime download changes over
- Cherry pick changes to the arcade SB template over (making the next update a noop and unblocking P7+)
- Hoist out the variable groups and parameters needed for the internal download to the top level yaml file.
- Remove the old DownloadFile task and replace this with the Arcade version. Specifically this allows us to remove
set/use of the DOTNETCLIMSRC_READ_SAS_TOKEN environment variable and instead rely on that task's ability to decode and
use a base64 encoded SAS token. The reason for the environment variable usage before was that the
non-encoded SAS token was getting mangled by msbuild/bash/etc. on non-Windows OSs.
- Update the source build tarball template with support for internal runtimes
Update to source build template
* Do not create .zip files on Linux/Mac
Avoid creating the .zip files on Linux/Mac, as they are not distributed or used in any scenario.
This saves > 20% of the total artifact size for this build (2.7 GB). Yay!
* Ensure output directories are created first
Context: https://github.com/dotnet/maui/pull/603
After building with `.\build.cmd -pack -publish`, I could install the
workload:
.\artifacts\bin\redist\Debug\dotnet\dotnet.exe workload install maui --verbosity diag
...
Successfully installed workload(s) maui.
Next, I setup a `global.json` with `6.0.100-dev` and tried:
.\artifacts\bin\redist\Debug\dotnet\dotnet.exe new maui
I was able to build and run the app, after some minor tweaks to the
template.
This is a cherry-pick of https://github.com/dotnet/installer/pull/10699 (which targets the public Installer repo, branch release/5.0.3xx) to the internal Installer repo, branch internal/release/5.0.3xx.
The public PR has been approved for 5.0.8 servicing.
- The stage has been subsumed by the aka.ms functionality and now can be removed.
- Clean up dead properties and functionality no longer needed because of it.
- Removing publishing of nupkg files as blobs. This used to be useful before because we often needed to get at the nupkgs in a flat, easy to copy format for pushing to the VS feed. But now the staging pipeline takes care of this, and moreover the use of post-build signing means that these files are not useful straight out of the build anyway. This should reduce publishing time and some post-build signing time.
Remove nupkg install in publishing.props
