Skip to content

Conversation

@eiriktsarpalis
Copy link
Member

@eiriktsarpalis eiriktsarpalis commented Jul 16, 2020

Cherry picks #39447 for the preview8 branch. Addresses #39444

@ghost
Copy link

ghost commented Jul 16, 2020

Tagging subscribers to this area: @tarekgh
Notify danmosemsft if you want to be subscribed.

Copy link

@pgovind pgovind left a comment

Choose a reason for hiding this comment

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

LGTM. I think System.Utf8String.Experimental.csproj also suffers from the same issue, but nobody has raised it yet, so maybe I'm wrong. I'll wait for Jan to confirm

@eiriktsarpalis
Copy link
Member Author

I'm going to merge this for now to unblock STEW builds. We can revisit if Utf8String has issues later.

@eiriktsarpalis eiriktsarpalis merged commit 0afe747 into dotnet:release/5.0-preview8 Jul 16, 2020
@eiriktsarpalis eiriktsarpalis deleted the fix-stew-build-preview8 branch July 16, 2020 17:29
<Nullable>enable</Nullable>
</PropertyGroup>
<PropertyGroup>
<PropertyGroup Condition="'$(TargetFramework)' == 'netcoreapp3.0' ">
Copy link

Choose a reason for hiding this comment

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

I should've caught this sooner. I'm wondering if this should be NETCOREAPPCURRENT instead of netcoreapp3.0?

Copy link
Member Author

Choose a reason for hiding this comment

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

In this case, no. If you take a look at the particular proj file, it is hardcoding netcoreapp3.0 in most places.

Copy link

Choose a reason for hiding this comment

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

Oh I see, you just refactored this. Still, the USE_INTERNAL_ACCESSIBILITY flag itself should be turned on only for NETCOREAPPCURRENT maybe?

Copy link

Choose a reason for hiding this comment

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

I think you can test this by trying both -f netcoreapp30 and -f netcoreapp50 locally

Copy link
Member Author

Choose a reason for hiding this comment

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

Nope, it's not needed. If you look at the item group at line 36, you'll see that the shims are only included for netcoreapp3.0.

@ghost ghost locked as resolved and limited conversation to collaborators Dec 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants