Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WASM] Content file of a uno library not be copied to the package_xxxx path at net9 #18925

Open
SongOfYouth opened this issue Nov 26, 2024 · 2 comments
Labels
difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification

Comments

@SongOfYouth
Copy link

Current behavior

the folder and file copied to bin\Debug\net9.0-browserwasm, but not bin\Debug\net9.0-browserwasm\wwwroot\package_xxxx when target to net9.

Expected behavior

Behaviers as what uno at net8

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

No response

Workaround

No response

Works on UWP/WinUI

Yes

Environment

Uno.UI / Uno.UI.WebAssembly / Uno.UI.Skia

NuGet package version(s)

Uno.Sdk: 5.5.43

Affected platforms

WebAssembly

IDE

Visual Studio 2022

IDE version

17.12.1

Relevant plugins

No response

Anything else we need to know?

It works at net8

@SongOfYouth SongOfYouth added difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification labels Nov 26, 2024
@SongOfYouth
Copy link
Author

UnoApp1.zip

@jeromelaban
Copy link
Member

Thanks for the report. It will be fixed with #18897.

Note that when running an non-publish build, the assets will not be in the output folder, as the static assets management is able to use assets in-place to improve build performance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification
Projects
None yet
Development

No branches or pull requests

2 participants