Skip to content

[browser][coreclr] - JSExport via single UCO instead of reflection, don't use AllowUnsafeBlocks #120215

Open
Open
[browser][coreclr] - JSExport via single UCO instead of reflection, don't use AllowUnsafeBlocks#120215
Assignees
pavelsavara
Labels
arch-wasmWebAssembly architecturearea-System.Runtime.InteropServices.JavaScriptos-browserBrowser variant of arch-wasm
Milestone
12.0.0

Description

@pavelsavara
pavelsavara
opened on Sep 29, 2025
  • use token for the method to resolve it.
  • consider backward compatibility
  • don't use <AllowUnsafeBlocks>true</AllowUnsafeBlocks>

Activity

  1. pavelsavara
    added this to the 11.0.0 milestone on Sep 29, 2025
  2. pavelsavara
    added
    arch-wasmWebAssembly architecture
    area-System.Runtime.InteropServices.JavaScript
    os-browserBrowser variant of arch-wasm
    on Sep 29, 2025

  3. dotnet-policy-service commented on Sep 29, 2025

    @dotnet-policy-service
    dotnet-policy-servicebot
    on Sep 29, 2025 – with Dotnet Policy Service
    Contributor

    Tagging subscribers to 'arch-wasm': @lewing, @pavelsavara
    See info in area-owners.md if you want to be subscribed.

  4. pavelsavara
    self-assigned this
    on Dec 2, 2025
  5. pavelsavara
    modified the milestones: 11.0.0, Future on Jan 27, 2026
  6. pavelsavara
    changed the title [-][browser][coreclr] - JSExport via single UCO instead of reflection[/-] [+][browser][coreclr] - JSExport via single UCO instead of reflection, don't use AllowUnsafeBlocks[/+] on Jan 28, 2026
  7. pavelsavara
    modified the milestones: Future, 12.0.0 on Jul 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

arch-wasmWebAssembly architecturearea-System.Runtime.InteropServices.JavaScriptos-browserBrowser variant of arch-wasm

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions