Skip to content

The browser-wasm SDK should automatically reference the threading/perf-tracing ref assemblies #72872

Closed

Description

@lambdageek

Some property property that uses the multithreaded runtime pack for the runtime artifacts and that adds a <PackageReference Include="Microsoft.NET.WebAssembly.Threading" IncludeAssets="compile" PrivateAssets="none" /> package to use the right ref assemblies.

And the same thing for the perftrace runtime pack and the System.Diagnostics.Tracing.WebAssembly.PerfTracing ref assemblies

Activity

  1. ghost added
    untriagedNew issue has not been triaged by the area owner
    on Jul 26, 2022
  2. added
    arch-wasmWebAssembly architecture
    and removed
    untriagedNew issue has not been triaged by the area owner
    on Jul 26, 2022
  3. added this to the 8.0.0 milestone on Jul 26, 2022
  4. lambdageek commented on Jul 26, 2022

    @lambdageek
    MemberAuthor

    I think this is @radical 's #72815

  5. lewing commented on Jul 26, 2022

    @lewing
    Member

    it is #72412 but yes that is blocked on wbt at the moment

  6. radical commented on Jul 27, 2022

    @radical
    Member

    The ref assemblies should be same for all the 3 variants, correct?

  7. lambdageek commented on Jul 27, 2022

    @lambdageek
    MemberAuthor

    we have extra ref assemblies (Microsoft.NET.WebAssembly.Threading and System.Diagnostics.Tracing.WebAssembly.PerfTracing). Original plan was to place these in separate nugets that would get referenced when a user .csproj did some gesture. Does that make sense to do as part of the work you're doing?

    I tried this out and it seemed to work (compilation would use the ref assemblies from the nugets, not the ones in the base SDK)

    if we're doing different runtime packs, I'm not sure if it's possible to place ref assemblies into the runtime packs directly. that might be simpler.

  8. radical commented on Jul 27, 2022

    @radical
    Member

    we have extra ref assemblies (Microsoft.NET.WebAssembly.Threading and System.Diagnostics.Tracing.WebAssembly.PerfTracing). Original plan was to place these in separate nugets that would get referenced when a user .csproj did some gesture. Does that make sense to do as part of the work you're doing?

    So, we need 3 ref pack nugets then?

  9. radical commented on Jul 27, 2022

    @radical
    Member

    We also need a few Wasm.Build.Tests to exercise using the threaded runtimes, and the extra ref assemblies.

  10. lambdageek commented on Jul 27, 2022

    @lambdageek
    MemberAuthor

    we have extra ref assemblies (Microsoft.NET.WebAssembly.Threading and System.Diagnostics.Tracing.WebAssembly.PerfTracing). Original plan was to place these in separate nugets that would get referenced when a user .csproj did some gesture. Does that make sense to do as part of the work you're doing?

    So, we need 3 ref pack nugets then?

    No? we need the SDK to add a PackageReference to one of the two new nugets when the corresponding runtime variant is selected that just has the handful of updated ref assemblies.

  11. radical commented on Jul 28, 2022

    @radical
    Member
    • What would be a good test to confirm that the correct runtime is being used?
    • For the extra ref assemblies, I guess, we could use something from them
  12. lambdageek commented on Sep 14, 2022

    @lambdageek
    MemberAuthor

    This is now mostly done (see https://github.com/lambdageek/hithread)

    I think the only remaining thing is to automatically add a <PackageReference Include=Microsoft.NET.WebAssembly.Threading"/> that will pull in the threading-enabled reference assemblies which will quiet down the platform compatibility analyzer warnings about "unsupported" threading operations

    https://github.com/lambdageek/hithread/blob/f7118d19ac88472576bd55671a33cfe9e5c2c099/hithread.csproj#L25

  13. changed the title [-]The browser-wasm SDK should support using multithread and perftrace runtime variants.[/-] [+]The browser-wasm SDK should automatically reference the threading/perf-tracing ref assemblies[/+] on Oct 12, 2022
  14. lewing commented on Jul 22, 2023

    @lewing
    Member

    done

  15. ghost locked as resolved and limited conversation to collaborators on Aug 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions