* Initial checkin of source-build tarball build infra
* Add a couple more comments
* Update eng/SourceBuild.Version.Details.xml based on PR review
Co-authored-by: Chris Rummel <crummel@microsoft.com>
* Updates based on PR review comments
Co-authored-by: Chris Rummel <crummel@microsoft.com>
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.
* Revert "Ensure copy latest runs on dotnet engine and not msbuild (#10766)"
This reverts commit d1be03eb6c.
* Revert "Publish additional files in official CI build"
This reverts commit 2e0eea8da3.
* Revert "Create WASM installers for optional workloads (#10685)"
This reverts commit 7c79ce28bc.
- 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
[main] Update dependencies from dotnet/sdk
- Coherency Updates:
- Microsoft.WindowsDesktop.App.Ref: from 6.0.0-preview.5.21262.4 to 6.0.0-preview.5.21263.2 (parent: Microsoft.NET.Sdk)
- VS.Redist.Common.WindowsDesktop.SharedFramework.x64.6.0: from 6.0.0-preview.5.21262.4 to 6.0.0-preview.5.21263.2 (parent: Microsoft.NET.Sdk)
- VS.Redist.Common.NetCore.SharedFramework.x64.6.0: from 6.0.0-preview.5.21263.1 to 6.0.0-preview.5.21263.11 (parent: Microsoft.NET.Sdk)
- Microsoft.NETCore.App.Ref: from 6.0.0-preview.5.21263.1 to 6.0.0-preview.5.21263.11 (parent: Microsoft.NET.Sdk)
- Microsoft.NETCore.App.Runtime.win-x64: from 6.0.0-preview.5.21263.1 to 6.0.0-preview.5.21263.11 (parent: Microsoft.NET.Sdk)
- Microsoft.NETCore.App.Host.win-x64: from 6.0.0-preview.5.21263.1 to 6.0.0-preview.5.21263.11 (parent: Microsoft.NET.Sdk)
- Microsoft.NETCore.DotNetHostResolver: from 6.0.0-preview.5.21263.1 to 6.0.0-preview.5.21263.11 (parent: Microsoft.NET.Sdk)
- Microsoft.NETCore.Platforms: from 6.0.0-preview.5.21263.1 to 6.0.0-preview.5.21263.11 (parent: Microsoft.NET.Sdk)
- Microsoft.AspNetCore.App.Ref: from 6.0.0-preview.5.21263.4 to 6.0.0-preview.5.21264.3 (parent: Microsoft.NET.Sdk)
- Microsoft.AspNetCore.App.Ref.Internal: from 6.0.0-preview.5.21263.4 to 6.0.0-preview.5.21264.3 (parent: Microsoft.NET.Sdk)
- Microsoft.AspNetCore.App.Runtime.win-x64: from 6.0.0-preview.5.21263.4 to 6.0.0-preview.5.21264.3 (parent: Microsoft.NET.Sdk)
- VS.Redist.Common.AspNetCore.SharedFramework.x64.6.0: from 6.0.0-preview.5.21263.4 to 6.0.0-preview.5.21264.3 (parent: Microsoft.NET.Sdk)
- dotnet-dev-certs: from 6.0.0-preview.5.21263.4 to 6.0.0-preview.5.21264.3 (parent: Microsoft.NET.Sdk)
- dotnet-user-secrets: from 6.0.0-preview.5.21263.4 to 6.0.0-preview.5.21264.3 (parent: Microsoft.NET.Sdk)
- Microsoft.DotNet.Common.ItemTemplates: from 6.0.100-preview.5.21263.2 to 6.0.100-preview.5.21264.1 (parent: Microsoft.NET.Sdk)
- Microsoft.WindowsDesktop.App.Runtime.win-x64: from 6.0.0-preview.5.21262.4 to 6.0.0-preview.5.21263.2 (parent: Microsoft.NET.Sdk)
- Microsoft.WindowsDesktop.App.Runtime.win-x64: from 6.0.0-preview.5.21262.4 to 6.0.0-preview.5.21263.2 (parent: Microsoft.NET.Sdk)
- Microsoft.DotNet.Wpf.ProjectTemplates: from 6.0.0-preview.5.21262.3 to 6.0.0-preview.5.21263.1 (parent: Microsoft.WindowsDesktop.App.Runtime.win-x64)
- Microsoft.Net.Compilers.Toolset: from 4.0.0-2.21263.6 to 4.0.0-2.21264.4 (parent: Microsoft.NET.Sdk)
- Do not cross-gen rzc tool
Context: https://github.com/dotnet/designs/pull/188/files#diff-8fcaa29d8e6f00b34b3cb1830d93f33e75f04424780a66a3c658c7021048e74fR125
Context: https://github.com/xamarin/xamarin-android/pull/5898
Context: https://github.com/xamarin/xamarin-macios/pull/11436
The Xamarin workload manifest packages have been renamed to have a `$(PackageId)` of:
Microsoft.NET.Sdk.[platform].Manifest-6.0.100
The `dotnet` directory on disk is expected to contain:
dotnet\sdk-manifests\6.0.100\Microsoft.NET.Sdk.[platform]\
WorkloadManifest.json
WorkloadManifest.targets
I manually tested `.\build.cmd -pack -publish` which produced
`artifacts\**\dotnet-sdk-6.0.100-dev-win-x64.exe`. After installing
it, I can see the "advertising manifest" feature seems to be working:
> dotnet workload install microsoft-android-sdk-full --configfile NuGet.config
Updated advertising manifest microsoft.net.sdk.android.
Updated advertising manifest microsoft.net.sdk.ios.
Updated advertising manifest microsoft.net.sdk.maccatalyst.
Updated advertising manifest microsoft.net.sdk.macos.
Updated advertising manifest microsoft.net.sdk.tvos.
Failed to update the advertising manifest microsoft.net.workload.blazorwebassembly: microsoft.net.workload.blazorwebassembly.manifest-6.0.100 is not found in NuGet feeds https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet6/nuget/v3/index.json, https://pkgs.dev.azure.com/azure-public/vside/_packaging/xamarin-impl/nuget/v3/index.json, https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-public/nuget/v3/index.json",
Installing pack Microsoft.Android.Sdk version 11.0.200-ci.main.256...
Writing workload pack installation record for Microsoft.Android.Sdk version 11.0.200-ci.main.256...
Installing pack Microsoft.Android.Sdk.BundleTool version 11.0.200-ci.main.256...
Writing workload pack installation record for Microsoft.Android.Sdk.BundleTool version 11.0.200-ci.main.256...
Installing pack Microsoft.Android.Ref version 11.0.200-ci.main.256...
Writing workload pack installation record for Microsoft.Android.Ref version 11.0.200-ci.main.256...
Installing pack Microsoft.Android.Templates version 11.0.200-ci.main.256...
Writing workload pack installation record for Microsoft.Android.Templates version 11.0.200-ci.main.256...
Garbage collecting for SDK feature bands 6.0.100...
Successfully installed workload(s) microsoft-android-sdk-full.
Then I'm able to build and run an Android application using the installed workload:
> dotnet build HelloAndroid -t:Run
...
Build succeeded.
0 Warning(s)
0 Error(s)
Time Elapsed 00:00:21.76
[main] Update dependencies from dotnet/sdk
- Coherency Updates:
- Microsoft.WindowsDesktop.App.Ref: from 6.0.0-preview.3.21172.2 to 6.0.0-preview.4.21175.1 (parent: Microsoft.NET.Sdk)
- VS.Redist.Common.WindowsDesktop.SharedFramework.x64.6.0: from 6.0.0-preview.3.21172.2 to 6.0.0-preview.4.21175.1 (parent: Microsoft.NET.Sdk)
- VS.Redist.Common.NetCore.SharedFramework.x64.6.0: from 6.0.0-preview.3.21167.1 to 6.0.0-preview.4.21176.1 (parent: Microsoft.NET.Sdk)
- Microsoft.NETCore.App.Ref: from 6.0.0-preview.3.21167.1 to 6.0.0-preview.4.21176.1 (parent: Microsoft.NET.Sdk)
- Microsoft.NETCore.App.Runtime.win-x64: from 6.0.0-preview.3.21167.1 to 6.0.0-preview.4.21176.1 (parent: Microsoft.NET.Sdk)
- Microsoft.NETCore.App.Host.win-x64: from 6.0.0-preview.3.21167.1 to 6.0.0-preview.4.21176.1 (parent: Microsoft.NET.Sdk)
- Microsoft.NETCore.DotNetHostResolver: from 6.0.0-preview.3.21167.1 to 6.0.0-preview.4.21176.1 (parent: Microsoft.NET.Sdk)
- Microsoft.NETCore.Platforms: from 6.0.0-preview.3.21167.1 to 6.0.0-preview.4.21176.1 (parent: Microsoft.NET.Sdk)
- Microsoft.AspNetCore.App.Ref: from 6.0.0-preview.3.21172.8 to 6.0.0-preview.4.21176.2 (parent: Microsoft.NET.Sdk)
- Microsoft.AspNetCore.App.Ref.Internal: from 6.0.0-preview.3.21172.8 to 6.0.0-preview.4.21176.2 (parent: Microsoft.NET.Sdk)
- Microsoft.AspNetCore.App.Runtime.win-x64: from 6.0.0-preview.3.21172.8 to 6.0.0-preview.4.21176.2 (parent: Microsoft.NET.Sdk)
- VS.Redist.Common.AspNetCore.SharedFramework.x64.6.0: from 6.0.0-preview.3.21172.8 to 6.0.0-preview.4.21176.2 (parent: Microsoft.NET.Sdk)
- dotnet-dev-certs: from 6.0.0-preview.3.21172.8 to 6.0.0-preview.4.21176.2 (parent: Microsoft.NET.Sdk)
- dotnet-user-secrets: from 6.0.0-preview.3.21172.8 to 6.0.0-preview.4.21176.2 (parent: Microsoft.NET.Sdk)
- Microsoft.DotNet.Common.ItemTemplates: from 6.0.100-preview.3.21161.1 to 6.0.100-preview.4.21176.3 (parent: Microsoft.NET.Sdk)
- Microsoft.WindowsDesktop.App.Runtime.win-x64: from 6.0.0-preview.3.21172.2 to 6.0.0-preview.4.21175.1 (parent: Microsoft.NET.Sdk)
- Microsoft.WindowsDesktop.App.Runtime.win-x64: from 6.0.0-preview.3.21172.2 to 6.0.0-preview.4.21175.1 (parent: Microsoft.NET.Sdk)
- Microsoft.DotNet.Wpf.ProjectTemplates: from 6.0.0-preview.3.21171.2 to 6.0.0-preview.4.21174.2 (parent: Microsoft.WindowsDesktop.App.Runtime.win-x64)
- Microsoft.NET.ILLink.Tasks: from 6.0.100-preview.2.21172.2 to 6.0.100-preview.2.21174.1 (parent: Microsoft.NET.Sdk)
- Microsoft.Net.Compilers.Toolset: from 3.10.0-2.21173.26 to 3.10.0-2.21175.26 (parent: Microsoft.NET.Sdk)
- Microsoft.Build: from 16.10.0-preview-21173-01 to 16.10.0-preview-21175-01 (parent: Microsoft.NET.Sdk)
- Remove Android, iOS, and macCatalyst from CA1416 analyzer warnings
- Merge remote-tracking branch 'origin/main' into darc-main-3ea62347-a0cb-4e6d-8270-37add6b236fa
- Missed property use
* Move dotnet-sdk snaps from dotnet/runtime
Dotnet/runtime was the home of the snap files for both dotnet-runtime
dotnet dotnet-sdk snap files. Moving the dotnet-sdk snap files into
dotnet/installer next to the installers.
* Create CODEOWNERS
In our efforts to unify the build access story using aka.ms links, we have found that there are certain files that share the same name in multiple different repositories, most importantly, productVersion.txt. As part of the work to move to aka.ms links, we will be flattening the short link paths, so rather than having a runtime-specific, aspnetcore-specific, etc. full path to the files generated by each of the repos, they will all go to the same short link location. This means that the path to productVersion.txt will collide in the aka.ms links (the backing locations are not changing and will be unaffected). To combat this, we will add a duplicate of each of the product repos productVersion.txt, renamed to indicate which product repo it came from, in this case installer-productVersion.txt. The original will remane so that we do not break existing scenarios that do not use the aka.ms links.
In our efforts to unify the build access story using aka.ms links, we have found that there are certain files that share the same name in multiple different repositories, most importantly, productVersion.txt. As part of the work to move to aka.ms links, we will be flattening the short link paths, so rather than having a runtime-specific, aspnetcore-specific, etc. full path to the files generated by each of the repos, they will all go to the same short link location. This means that the path to productVersion.txt will collide in the aka.ms links (the backing locations are not changing and will be unaffected). To combat this, we will add a duplicate of each of the product repos productVersion.txt, renamed to indicate which product repo it came from, in this case installer-productVersion.txt. The original will remane so that we do not break existing scenarios that do not use the aka.ms links.
