FastUpToDate: Up-to-date check threw an exception. Not up-to-date. System.ArgumentNullException: Value cannot be null.

[PetrNecasSE]

Hello, when building an empty MSI Installer package I'm getting following error:

1>FastUpToDate: Up-to-date check threw an exception. Not up-to-date. System.ArgumentNullException: Value cannot be null.
1>Parameter name: path1
1> at System.IO.Path.Combine(String path1, String path2)
1> at Microsoft.VisualStudio.ProjectSystem.VS.UpToDate.BuildUpToDateCheck.<>c__DisplayClass47_0.<g__CheckAsync|0>d.MoveNext() (Package1)
1>------ Build started: Project: Package1, Configuration: Debug x86 ------
1>Package1 -> C:\Users\user\source\repos\2025-04-17\Package1\Package1\bin\x86\Debug\en-US\Package1.msi
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Build completed at 11:42 AM and took 00.316 seconds ==========
WARNING: Potential build performance issue in 'Package1.wixproj'. The project does not appear up-to-date after a successful build: Up-to-date check threw an exception. Not up-to-date. System.ArgumentNullException: Value cannot be null.
Parameter name: path1
at System.IO.Path.Combine(String path1, String path2)
at Microsoft.VisualStudio.ProjectSystem.VS.UpToDate.BuildUpToDateCheck.<>c__DisplayClass47_0.<g__CheckAsync|0>d.MoveNext(). See https://aka.ms/incremental-build-failure.

Looks to be the same as reported here: dotnet/project-system#9348

Does anyone else experience this issue?

[robmen]

Yep. You see it when you enable detailed build logging in VS. Supporting "fast update check" is a low-pri item to implement in HeatWave. It's just one more feature where VS can break us (FireGiant). 😅