-
Notifications
You must be signed in to change notification settings - Fork 839
Description
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