-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Remove Blazor WASM SDK from repo #29427
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
Changes from all commits
6c4a773
555c401
fbe1288
6807ab2
0f7c674
5cd2bda
193c562
959b987
5eedf68
0c5305c
686fb0b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -29,4 +29,11 @@ | |
<!-- Ignore warning about calling the Pack target on Web SDK projects. Our build scripts call /t:pack on everything in this repo. --> | ||
<WarnOnPackingNonPackableProject>false</WarnOnPackingNonPackableProject> | ||
</PropertyGroup> | ||
|
||
<!-- The SDK includes some conflict resolution targets that check for duplicate items in the publish targets. It's very greedy | ||
and ends up marking the same files in different projects as duplicates of each other. We disable this check here to work | ||
around this issue. --> | ||
<PropertyGroup> | ||
<ErrorOnDuplicatePublishOutputFiles>false</ErrorOnDuplicatePublishOutputFiles> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why is this now an issue❔ If anything, the build should run smoother without the Blazor WASM SDK. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We bumped the version of the SDK we are one and picked up a change to the conflict resolution targets mention here so this workaround is necessary since this is new code. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is this necessary everywhere (as it is now) or just in a couple of projects❔ Having it here concerns me… There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This only affects a couple of projects, particularly the test sites that we use which end up having a lot of common files (wwwroot/style.css for example) which trigger this buggy code path. I'm working on opening a bug in the SDK repo to see if there is an issue with this. |
||
</PropertyGroup> | ||
</Project> |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,7 +2,7 @@ | |
|
||
<PropertyGroup> | ||
<OutputType>Exe</OutputType> | ||
<TargetFramework>net5.0</TargetFramework> | ||
<TargetFramework>net6.0</TargetFramework> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why is this changing here❔ We've been intentionally using the older TFM since the There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I had to update the runtime when updating the SDK and was trying to fix the following issue:
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That sounds like a side effect of the SDK no longer bundling the runtimes though it might be a bug in the specific version. @dsplaisted any suggestions❔ |
||
</PropertyGroup> | ||
|
||
<ItemGroup> | ||
|
Large diffs are not rendered by default.
This file was deleted.
This file was deleted.
Uh oh!
There was an error while loading. Please reload this page.