-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Use wasm and js integration for unsupported systems #89500
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsDescriptionIn our country people cant used latest technology utilities Reproduction StepsMigrate from .net 7 to .net 8 and use windows 7 Expected behaviorApplication is nit running Actual behaviorApplication must be check browser version and run specific version of that Regression?No response Known WorkaroundsNo response ConfigurationNo response Other informationNo response
|
this appears to be a duplicate of #89028 and the discussion is happening there |
Windows 7 support ended on January 14, 2020 You can use wasm-tools workload and recompille the application without SIMD and EH instructions.
|
Description
In our country people cant used latest technology utilities
For example we have customer with windows 7 and cpu dual core!
We cant force them to bought new system for our applications
We must be consider continued support them
In blazor must be used new features that check if browser is not compatible with blazor requirements like simd that our customers doesnt have problem with .net 7 but in .net 8 with this requirement many of them cant be used our system
We must be avoid to happen that problems when migrating from old version to new version
Reproduction Steps
Migrate from .net 7 to .net 8 and use windows 7
Expected behavior
Application is nit running
Actual behavior
Application must be check browser version and run specific version of that
Regression?
No response
Known Workarounds
No response
Configuration
No response
Other information
No response
The text was updated successfully, but these errors were encountered: