-
-
Notifications
You must be signed in to change notification settings - Fork 1k
[wasm] Set the right runtime moniker #1932
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
Conversation
Fix dotnet/performance#2250 Commit 80f45ce started using the runtime moniker to decide, which main JS file to use. We use `test-main.js` in net7.0, while we were using `main.js` in older versions. To make that work, let set the right runtime moniker to WasmRuntime. So that later in `Executor::ProcessStartInfo` we select the right file.
adamsitnik
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thank you @radekdoulik !
| default: | ||
| return false; | ||
| } | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in the future we might want to move it to RuntimeMonikerExtensions
|
Looks good to me. |
|
The Is that new fail? From quick look it seems unrelated. |
|
Actually I see it fail elsewhere too, so it is not related to this change. |
Fix dotnet/performance#2250
Commit 80f45ce started using the runtime moniker to decide, which
main JS file to use. We use
test-main.jsin net7.0, while we wereusing
main.jsin older versions.To make that work, let set the right runtime moniker to
WasmRuntime. Sothat later in
Executor::ProcessStartInfowe select the right file.