Warning when building 1.8experimental2.

[KevinLaMS]

Describe the bug

Morten reports:
However there's a pretty big issue that might need some quick resolution: The WinUI package is depending on 1.8.250506001-experimental of the InteractiveExperiences package which doesn't exist.

This causes build issues in the build when just referencing the WinUI package.

Steps to reproduce the bug

Update project to latest experimental.
Have warnings break the build.
Observer error

Expected behavior

No response

Screenshots

No response

NuGet package version

None

Packaging type

No response

Windows version

No response

IDE

No response

Additional context

No response

[KevinLaMS]

This is a known issue with the experimental build:

When using the WindowsAppSDK component packages, you may notice a warning NU1603 indicating the specified version of a dependent component package was not found, but another was resolved instead. This is expected with the experimental2 build and NuGet will correctly resolve a newer version of the package which will allow your project to build. If you treat warnings as errors, you can temporarily treat this specific warning as not an error by specifying the property <WarningsNotAsErrors>NU1603</WarningsNotAsErrors>.

We will have strict versioning in the next release, to ensure consistent dependencies across the package graph.

[dotMorten]

Hah thanks for beating me to it. Was about to log this :-)

[RDMacLachlan]

The readme has been updated.

[guimafelipe]

I tried to repro this on different experimental builds and couldn't repro the errors.

[dotMorten]

@guimafelipe This is a confusing response when @KevinLaMS already confirmed this as a known issue.

[dotMorten]

Easy repro. Run a dotnet restore on this project:

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net8.0-windows10.0.19041.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.WindowsAppSDK.WinUI" Version="1.8.250507002-experimental" /> 
  </ItemGroup>
</Project>

This is however fixed with version 1.8.250701000-experimental