WASM Platform must not target netstandard2.0 #14
Labels
kind/enhancement
New feature or request
platform/wasm 🌐
Categorizes an issue or PR as relevant to the WebAssembly platform
Comments
|
Is this why Prism and other libraries can't be added to the .NET Standard project? |
|
This is the main reason, yes. Many libraries do have an actual .NET Standard 2.0 target, and making it an alias of WebAssembly is a recipe for confusing users. That being said, it's possible to make Uno specific packages but the ultimate goal would be to have only one package for Prism.Windows, for instance. |
ghuntley
added
platform/wasm 🌐
|
This issue is no longer relevant, as |
19 tasks
jeromelaban
pushed a commit
that referenced
this issue
Apr 21, 2021
This is a edge case on Linux that for some reason do not auto refresh the new content of the file created. So, we are refreshing the content on the extension side to be sure that the file will load with template code. Related-to: #14 Signed-off-by: Matheus Castello <matheus@castello.eng.br>
lukeblevins
pushed a commit
to lukeblevins/uno
that referenced
this issue
Jan 17, 2024
* chore: renamed targets file * chore: renamed namespaces and file names * chore: Renamed the namespaces inside Resizetizer project and all the references
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current WebAssembly target is currently using netstandard 2.0 for deployment.
This is fine for now as Uno does not support .NET Standard 2.0 as a platform target, so wasm specific code is using NETSTANDARD2_0 to target it.
This should be addressed somehow by NuGet/NuGet.Client#2159.
Update: NuGet/Home#8186
The text was updated successfully, but these errors were encountered: