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

[browser][MT] Blazor E2E test with MT runtime #48925

Closed
pavelsavara opened this issue Jun 20, 2023 · 3 comments
Closed

[browser][MT] Blazor E2E test with MT runtime #48925

pavelsavara opened this issue Jun 20, 2023 · 3 comments
Assignees
Labels
arch-wasm area-blazor Includes: Blazor, Razor Components ✔️ Resolution: Duplicate Resolved as a duplicate of another issue Pillar: Dev Experience Priority:1 Work that is critical for the release, but we could probably ship without Status: Resolved

Comments

@pavelsavara
Copy link
Member

pavelsavara commented Jun 20, 2023

Build the test app with experimental MT workload

To unit test that

  • the app could start (with cop headers)

Later scenarios are (we are not ready yet)

cc @javiercn

@pavelsavara pavelsavara added area-blazor Includes: Blazor, Razor Components arch-wasm labels Jun 20, 2023
@pavelsavara pavelsavara added this to the .NET 8.0 milestone Jun 20, 2023
@mkArtakMSFT mkArtakMSFT modified the milestones: .NET 8.0, 8.0 Jun 29, 2023
@wtgodbe wtgodbe modified the milestones: 8.0, 8.0.0 Oct 3, 2023
@mkArtakMSFT mkArtakMSFT modified the milestones: 8.0.0, .NET 9 Planning Oct 4, 2023
@ghost
Copy link

ghost commented Oct 4, 2023

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

@ghost
Copy link

ghost commented Dec 29, 2023

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

@mkArtakMSFT mkArtakMSFT added Priority:1 Work that is critical for the release, but we could probably ship without Pillar: Dev Experience and removed Pillar: Technical Debt labels Jan 8, 2024
@mkArtakMSFT
Copy link
Member

Closing this as a dupe of #53435 as we're including it into .NET 9 plans.

@mkArtakMSFT mkArtakMSFT closed this as not planned Won't fix, can't repro, duplicate, stale Jan 30, 2024
@mkArtakMSFT mkArtakMSFT added the ✔️ Resolution: Duplicate Resolved as a duplicate of another issue label Jan 30, 2024
@ghost ghost added the Status: Resolved label Jan 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
arch-wasm area-blazor Includes: Blazor, Razor Components ✔️ Resolution: Duplicate Resolved as a duplicate of another issue Pillar: Dev Experience Priority:1 Work that is critical for the release, but we could probably ship without Status: Resolved
Projects
None yet
Development

No branches or pull requests

5 participants