Skip to content

Image change is causing incorrect build output #14162

@JSparshottO2

Description

@JSparshottO2

Description

we are requesting a windows-latest image in our build pipeline.

We are using vsbuild@1 to run an Appx build task like this:

- task: VSBuild@1
    displayName: Build to Appx
    inputs:
      platform: 'x64' 
      solution: '**/*.slnx'
      configuration: 'Release'
      msbuildArgs: '/p:AppxBundlePlatforms="x64" /p:AppxPackageDir="${{ parameters.appxPackageDir }}" /p:AppxBundle=Always /p:UapAppxPackageBuildMode=SideLoadOnly /p:AppxPackageSigningEnabled=false /p:Company="Our Company"'

between image version 20260510.128.1 and 20260518.141.1 something has changed which is causing the Appx bundle that is produced to be missing some core dependencies (in this situation we reference MahApps.Metro). version 20260518.141.1 of the runner image simply doesn't package that dependency through the vsbuild task.

The vsbuild task appears to be the same on both image versions, 1.273.0.

I appreciate you may need more diagnostics information to investigate this, which I'm happy to provide. I just don't know exactly what is useful to provide right now, and I certainly don't want to be dumping the entire build log out :D

Platforms affected

  • Azure DevOps
  • GitHub Actions - Standard Runners
  • GitHub Actions - Larger Runners

Runner images affected

  • Ubuntu 22.04
  • Ubuntu 24.04
  • Ubuntu Slim
  • macOS 14
  • macOS 14 Arm64
  • macOS 15
  • macOS 15 Arm64
  • macOS 26
  • macOS 26 Arm64
  • Windows Server 2022
  • Windows Server 2025
  • Windows Server 2025 with Visual Studio 2026

Image version and build link

20260213.493

Is it regression?

yes, previous version that worked was 20260415.520

Expected behavior

All dependencies to be included in the resulted package from vsbuild task

Actual behavior

Some dependencies missing.

Repro steps

use latest runner image

Metadata

Metadata

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions