From 4564c40d629e9368156a5271c49c1ef3eadf2ef4 Mon Sep 17 00:00:00 2001 From: Matthew John Cheetham Date: Tue, 12 May 2026 09:49:03 +0100 Subject: [PATCH 1/2] azure-pipelines: move to new MicroBuild pool Move from the VSEngSS-MicroBuild2022-1ES pool to the new VSEng-MicroBuildVSStable pool, which has Windows Server 2025 + Visual Studio 2026 images instead. Signed-off-by: Matthew John Cheetham --- .azure-pipelines/release.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.azure-pipelines/release.yml b/.azure-pipelines/release.yml index c7454f322..7350735bc 100644 --- a/.azure-pipelines/release.yml +++ b/.azure-pipelines/release.yml @@ -25,7 +25,7 @@ extends: template: azure-pipelines/MicroBuild.1ES.Official.yml@MicroBuildTemplate parameters: pool: - name: VSEngSS-MicroBuild2022-1ES + name: VSEng-MicroBuildVSStable featureFlags: incrementalSDLBinaryAnalysis: false From 3e5fb28d5fbd69d1205390c956300ac29da7de67 Mon Sep 17 00:00:00 2001 From: Tyrie Vella Date: Tue, 12 May 2026 11:34:07 -0700 Subject: [PATCH 2/2] Fix FastFetch MicroBuild signing for NativeAOT publish With PublishAot=true, dotnet publish produces the native executable in $(PublishDir) rather than $(OutputPath). The FilesToSign items were still referencing $(OutputPath)\FastFetch.exe, causing the ESRP signing task to fail because the file doesn't exist at that path. Change the signing path to $(PublishDir) and remove the managed DLL entries (GVFS.Common.dll, GVFS.Platform.Windows.dll, GVFS.Virtualization.dll) which are statically linked into the native AOT binary and no longer exist as separate files. Assisted-by: Claude Opus 4.6 Signed-off-by: Tyrie Vella --- GVFS/FastFetch/FastFetch.csproj | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/GVFS/FastFetch/FastFetch.csproj b/GVFS/FastFetch/FastFetch.csproj index ad8ec89a3..e99f7b785 100644 --- a/GVFS/FastFetch/FastFetch.csproj +++ b/GVFS/FastFetch/FastFetch.csproj @@ -16,11 +16,7 @@ - + Microsoft400 false