Skip to content

Conversation

@jjonescz
Copy link
Member

Closes #49925.

This reverts commit d429129.
@github-actions github-actions bot added the Area-AspNetCore RazorSDK, BlazorWebAssemblySDK, dotnet-watch label Jul 28, 2025
@dotnet-policy-service
Copy link
Contributor

Thanks for your PR, @@jjonescz.
To learn about the PR process and branching schedule of this repo, please take a look at the SDK PR Guide.

@jjonescz jjonescz marked this pull request as ready for review July 28, 2025 11:22
Copilot AI review requested due to automatic review settings July 28, 2025 11:22
@jjonescz jjonescz requested review from a team as code owners July 28, 2025 11:22
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR removes skip attributes from Razor and Blazor tests, re-enabling tests that were previously disabled due to issue #49925. The changes indicate that the underlying issue has been resolved and these tests can now run successfully.

  • Removes Skip parameter from RequiresMSBuildVersionFact attribute in Razor components test
  • Removes Skip parameter from WindowsOnlyRequiresMSBuildVersionFact attribute in Blazor legacy integration test

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
test/Microsoft.NET.Sdk.Razor.Tests/BuildWithComponentsIntegrationTest.cs Unskips desktop MSBuild test for Razor components
test/Microsoft.NET.Sdk.BlazorWebAssembly.Tests/BlazorLegacyIntegrationTest60.cs Unskips Windows-only publish test for Blazor WebAssembly hosted projects

@akoeplinger akoeplinger merged commit 1ed2f8e into dotnet:main Jul 28, 2025
29 checks passed
@jjonescz jjonescz deleted the unskip-razor-tests branch July 28, 2025 14:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area-AspNetCore RazorSDK, BlazorWebAssemblySDK, dotnet-watch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Some razor tests don't work due to System.Memory mismatch

2 participants