-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[wasm][mt] Fix few libraries projects #97539
[wasm][mt] Fix few libraries projects #97539
Conversation
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue DetailsAdd $(NetCoreAppCurrent)-browser TFM to System.Linq.Parallel.csproj and use the platform identifier Do not set FeatureWasmThreads in ref projects. These were never evaluated to true and we are building different set of these ref libraries in Microsoft.NET.WebAssembly.Threading.proj.
|
This is followup PR for #97505 All the libraries should be fine now.
and in the
|
src/libraries/System.Linq.Parallel/src/System.Linq.Parallel.csproj
Outdated
Show resolved
Hide resolved
Co-authored-by: Viktor Hofer <[email protected]>
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
Build browser-wasm linux Release LibraryTests_Threading_Smoke is #97546 |
Add $(NetCoreAppCurrent)-browser TFM to System.Linq.Parallel.csproj and use the platform identifier
Do not set FeatureWasmThreads in ref projects. These were never evaluated to true and we are building different set of these ref libraries in Microsoft.NET.WebAssembly.Threading.proj.