Re-enable blazor tests in 6.0 after 17.4 msbuild fix is in

[marcpopMSFT]

dotnet/sdk#28322 (comment)

[TanayParikh]

@marcpopMSFT @dsplaisted do we know when the 17.4 fix will be in? Is it just a matter of dependency flow, or do we need to take additional action?

fyi/ @javiercn

[marcpopMSFT]

I think it needs to be in the helix images the tests run in. It kind of looks like from the history that this probably made it in for preview 3 of 17.4 but isn't in RC2 of the SDK. Since this issue broke because of the helix images, I think getting them updated to preview 3 may be sufficient.

@MattGal might know the schedule but I think it usually takes ~2 weeks from release to being adopted in the helix queues.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 8 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.

[MattGal]

I think it needs to be in the helix images the tests run in. It kind of looks like from the history that this probably made it in for preview 3 of 17.4 but isn't in RC2 of the SDK. Since this issue broke because of the helix images, I think getting them updated to preview 3 may be sufficient.

@MattGal might know the schedule but I think it usually takes ~2 weeks from release to being adopted in the helix queues.

I missed this one back when I was originally tagged, but I would point out that the "regular" VS 2022 images are now at version 17.4.3, and you can see our upgrade schedule here

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 8 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]

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]

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.

[javiercn]

Done as part of dotnet/sdk#38261