-
Notifications
You must be signed in to change notification settings - Fork 461
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
[Info] dotnet ^7.0.2* introduced an MSBuild preview version with breaking changes. #383
Comments
hi @snwflake, thank you for the report, we will take a look at it :) |
Typo in your fix, should be -rf otherwise it errors with: |
@danielriddellsh sorry, should have copy&pasted. |
7.0.201 has been released but it’s not picked up by setup-dotnet. Anyone know what’s up? |
I just wanted to leave here that one of the workarounds described here worked for me. What I did was make use of a This fixed the issue for me without having to remove the default installation of dotnet SDK
|
6.0.* also has breaking issues with |
It's a terrible release, isn't it? |
My experience seems to be that running any Falling back to |
Hi, @tgrnwd 👋 The |
@IvanZosimov Ah, thank you. I'm certain I read this, but didn't fully understand at that time. |
I'm closing this issue as the NET SDK 7.0.201 was released and it seems to solve the problem. |
Description:
For reference: dotnet/sdk#30624
The MSBuild preview version provided with 7.0.200 introduced breaking changes and generally ill-formed behavior.
Pinning the version to anything below 7.0.200, ie. 7.0.103 does not resolve that issue, as the same MSBuild preview is still being used.
My workaround so far has been to add another step after the dotnet-setup which just removes 7.0.2* sdk versions. Only then started my build to produce working output with proper viewcomponents.
Task version:
926f442
Platform:
Runner type:
Repro steps:
Notes:
While this is a bug introduced by the SDK, I still wanted to raise this issue here, to spare others from wasting 3 hours debugging it.
The workaround for me is currently the following until the announced hotfix 7.0.201 goes live:
The text was updated successfully, but these errors were encountered: