[wasm] `browser-eventpipe` sample broken with `PerfTracing` build - `JSExportAttribute' is only supported on: 'browser'`

[radical]

This is reproducible on main. PerfTracing build on runtime-wasm:

/__w/1/s/src/mono/sample/wasm/browser-eventpipe/Program.cs(136,10): error CA1416: This call site is reachable on all platforms. 'JSExportAttribute' is only supported on: 'browser'. [/__w/1/s/src/mono/sample/wasm/browser-eventpipe/Wasm.Browser.EventPipe.Sample.csproj]
##[error]src/mono/sample/wasm/browser-eventpipe/Program.cs(136,10): error CA1416: (NETCORE_ENGINEERING_TELEMETRY=Build) This call site is reachable on all platforms. 'JSExportAttribute' is only supported on: 'browser'.
/__w/1/s/src/mono/sample/wasm/browser-eventpipe/Program.cs(142,10): error CA1416: This call site is reachable on all platforms. 'JSExportAttribute' is only supported on: 'browser'. [/__w/1/s/src/mono/sample/wasm/browser-eventpipe/Wasm.Browser.EventPipe.Sample.csproj]
##[error]src/mono/sample/wasm/browser-eventpipe/Program.cs(142,10): error CA1416: (NETCORE_ENGINEERING_TELEMETRY=Build) This call site is reachable on all platforms. 'JSExportAttribute' is only supported on: 'browser'.
/__w/1/s/src/mono/sample/wasm/browser-eventpipe/Program.cs(106,10): error CA1416: This call site is reachable on all platforms. 'JSExportAttribute' is only supported on: 'browser'. [/__w/1/s/src/mono/sample/wasm/browser-eventpipe/Wasm.Browser.EventPipe.Sample.csproj]
##[error]src/mono/sample/wasm/browser-eventpipe/Program.cs(106,10): error CA1416: (NETCORE_ENGINEERING_TELEMETRY=Build) This call site is reachable on all platforms. 'JSExportAttribute' is only supported on: 'browser'.

• The last working job runtime-wasm was https://dev.azure.com/dnceng-public/public/_build/results?buildId=49311&view=results
• And the first failing one seen was https://dev.azure.com/dnceng-public/public/_build/results?buildId=58245&view=results
• Since this job only runs in runtime-wasm, we don't know exactly which commit might have caused this.
• But looking at the commits, I think it might be 54c4a4b .

cc @lambdageek @pavelsavara

TODO:

• We should build the threading, and perftracing related samples on runtime pipeline too

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

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

Issue Details

---

This is reproducible on main. PerfTracing build on runtime-wasm:

/__w/1/s/src/mono/sample/wasm/browser-eventpipe/Program.cs(136,10): error CA1416: This call site is reachable on all platforms. 'JSExportAttribute' is only supported on: 'browser'. [/__w/1/s/src/mono/sample/wasm/browser-eventpipe/Wasm.Browser.EventPipe.Sample.csproj]
##[error]src/mono/sample/wasm/browser-eventpipe/Program.cs(136,10): error CA1416: (NETCORE_ENGINEERING_TELEMETRY=Build) This call site is reachable on all platforms. 'JSExportAttribute' is only supported on: 'browser'.
/__w/1/s/src/mono/sample/wasm/browser-eventpipe/Program.cs(142,10): error CA1416: This call site is reachable on all platforms. 'JSExportAttribute' is only supported on: 'browser'. [/__w/1/s/src/mono/sample/wasm/browser-eventpipe/Wasm.Browser.EventPipe.Sample.csproj]
##[error]src/mono/sample/wasm/browser-eventpipe/Program.cs(142,10): error CA1416: (NETCORE_ENGINEERING_TELEMETRY=Build) This call site is reachable on all platforms. 'JSExportAttribute' is only supported on: 'browser'.
/__w/1/s/src/mono/sample/wasm/browser-eventpipe/Program.cs(106,10): error CA1416: This call site is reachable on all platforms. 'JSExportAttribute' is only supported on: 'browser'. [/__w/1/s/src/mono/sample/wasm/browser-eventpipe/Wasm.Browser.EventPipe.Sample.csproj]
##[error]src/mono/sample/wasm/browser-eventpipe/Program.cs(106,10): error CA1416: (NETCORE_ENGINEERING_TELEMETRY=Build) This call site is reachable on all platforms. 'JSExportAttribute' is only supported on: 'browser'.

• The last working job runtime-wasm was https://dev.azure.com/dnceng-public/public/_build/results?buildId=49311&view=results
• And the first failing one seen was https://dev.azure.com/dnceng-public/public/_build/results?buildId=58245&view=results
• Since this job only runs in runtime-wasm, we don't know exactly which commit might have caused this.
• But looking at the commits, I think it might be 54c4a4b .

cc @lambdageek @pavelsavara

TODO:

• We should build the threading, and perftracing related samples on runtime pipeline too

Author:	radical
Assignees:	-
Labels:	arch-wasm, blocking-clean-ci-optional
Milestone:	-

[pavelsavara]

<RunAnalyzers>true</RunAnalyzers> makes the difference