[Wasm] .NET 9.0.102 fails with no value for parameter "OutputPackagePath"

[emem67]

Current behavior

I also tried to create a new empty solution with only windows and webassembly and I still get this:

MSB4044 The "GenerateUnoAssetsManifest_v05da712db32bc85a0fb32e039ff4b1d24a10ddbb" task was not given a value for the required parameter "OutputPackagePath". UnoApp1 (net9.0-browserwasm) C:\Users\xxxx.nuget\packages\uno.wasm.bootstrap\9.0.8\build\Uno.Wasm.Bootstrap.targets 270

I would like to understand if it is just me and the update to visual studio was just a coincidence.
Thanks

Expected behavior

it should compile

How to reproduce it (as minimally and precisely as possible)

Create a new Uno Platform project from VS
.net9
WebAssembly and Windows
MVVM XAML
Material theme
no extensions no navigation no features
build selecting WinAppSDK Unpackage

Workaround

very stupid, remove the webassembly target from the *.csproj

remove: net9.0-windows10.0.26100;net9.0-browserwasm
add : net9.0-windows10.0.26100

Works on UWP/WinUI

None

Environment

Windows 11 + VisualStudio to 17.12.14

NuGet package version(s)

"Uno.Sdk": "5.5.56"

Affected platforms

No response

IDE

No response

IDE version

No response

Relevant plugins

No response

Anything else we need to know?

No response

[jeromelaban]

Thanks for the report! We're not reproducing this issue. Could you provide a binlog of the error?

[emem67]

Here is the binlog
msbuild.binlog.zip

[jeromelaban]

Thanks, this helps. This is a breaking changes introduced in the .NET SDK 9.0.102. We'll take a look.

[jeromelaban]

As a workaround, you can install .NET 9.0.101, then modify the following global.json at the root of your solution to specify the version of .NET to use:

{
  "msbuild-sdks": {
    "Uno.Sdk": "5.5.56"
  },
  "sdk": {
    "version": "9.0.101",
    "rollForward": "disable"
  }
}

[jeromelaban]

Another possible workaround is to add the following to the csproj, without having to downgrade .NET:

<PropertyGroup>
	<UnoGenerateAssetsManifestDependsOn>
		$(UnoGenerateAssetsManifestDependsOn);
		GenerateUnoWasmAssets;
	</UnoGenerateAssetsManifestDependsOn>
</PropertyGroup>

[emem67]

Another possible workaround is to add the following to the csproj, without having to downgrade .NET:

$(UnoGenerateAssetsManifestDependsOn); GenerateUnoWasmAssets;

this is solving my issue, looking forward for the fix, many thanks for the support

[DierkDroth]

Another possible workaround is to add the following to the csproj, without having to downgrade .NET:

$(UnoGenerateAssetsManifestDependsOn); GenerateUnoWasmAssets;

Thanks @jeromelaban.
Would that section needed to be removed at a later point e.g. on official UNO 5.6 release?

[jeromelaban]

@DierkDroth no, but in your case, you can update to the latest uno.wasm.bootstrap 9.0.10 which includes the fix for this issue.

This issue is kept opened because the fix is not yet included in an uno.sdk release.

[DierkDroth]

Thanks for clarification @jeromelaban