Skip to content
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

Closed
sajjadarashhh opened this issue Jul 26, 2023 · 3 comments
Closed

Use wasm and js integration for unsupported systems #89500

sajjadarashhh opened this issue Jul 26, 2023 · 3 comments
Assignees
Labels
arch-wasm WebAssembly architecture area-VM-meta-mono
Milestone

Comments

@sajjadarashhh
Copy link

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

@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Jul 26, 2023
@ghost ghost added the untriaged New issue has not been triaged by the area owner label Jul 26, 2023
@jeffschwMSFT jeffschwMSFT added area-VM-meta-mono arch-wasm WebAssembly architecture labels Jul 26, 2023
@ghost
Copy link

ghost commented Jul 26, 2023

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

Issue Details

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

Author: sajjadarashhh
Assignees: -
Labels:

arch-wasm, untriaged, area-VM-meta-mono, needs-area-label

Milestone: -

@vcsjones vcsjones removed the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Jul 26, 2023
@lewing lewing added this to the 8.0.0 milestone Jul 26, 2023
@ghost ghost removed the untriaged New issue has not been triaged by the area owner label Jul 26, 2023
@lewing
Copy link
Member

lewing commented Jul 26, 2023

this appears to be a duplicate of #89028 and the discussion is happening there

@lewing lewing closed this as completed Jul 26, 2023
@pavelsavara
Copy link
Member

Windows 7 support ended on January 14, 2020

You can use wasm-tools workload and recompille the application without SIMD and EH instructions.

@ghost ghost locked as resolved and limited conversation to collaborators Aug 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
arch-wasm WebAssembly architecture area-VM-meta-mono
Projects
None yet
Development

No branches or pull requests

5 participants