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

.NET 9 Support #878

Closed
22 of 26 tasks
jeromelaban opened this issue Jul 31, 2024 · 0 comments · Fixed by #884
Closed
22 of 26 tasks

.NET 9 Support #878

jeromelaban opened this issue Jul 31, 2024 · 0 comments · Fixed by #884

Comments

@jeromelaban
Copy link
Member

jeromelaban commented Jul 31, 2024

Tracking for the migration to net9 wasm support:

  • Runtime Assets packaging
  • AOT Compiler packaging
  • Raytracer interpreter build
  • dotnet publish support
  • Native Assets
  • AOT Compilation
  • macOS cross AOT runtime support
  • uno-assets support
  • PG-AOT compilation (implies restoring the filtering tooling)
  • Linker descriptor compat
  • embedded mode
  • JSInvoke adjusments (Uno.UI specific for Uno.UI.Runtime.WebAssembly? See Bootsrapper.JSInvoke tentative in dev/jela/net9)
  • Threading WasmAppHost support
  • Restore devserver package for compat
  • Progress loading support
  • emcc Linker options (WasmShellEmccLinkOptimization and WasmShellEmccLinkOptimizationLevel)
  • Runtime log tracing (Possible inclusion of heap dumping in preview 7) [wasm] Enable the log profiler dotnet/runtime#107434
  • Version checker
  • Documentation
  • PWA
  • Restore Satellite assemblies validation
  • offline PWA
  • CSP WasmAppHost support
  • extension-less (may not be possible?)
  • adjust dotnet runtime reported version (42.42.42.42 or 9.0.0-dev)
  • Obfuscation (may not be needed with WebCIL and automatic .wasm extension)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant