Skip to content

Remove new Microsoft.NETCore.App.Ref targeting pack assemblies from WindowsDesktop targeting pack #1747

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

Merged
merged 1 commit into from
Jun 17, 2021

Conversation

ryalanms
Copy link
Member

Required by:

Expose missing references which are present in the runtime and in packages in the targeting pack #54147: dotnet/runtime#54147

Remove new Microsoft.NETCore.App.Ref targeting pack assemblies from WindowsDesktop targeting packs, and update versions.props to rebuild WindowsDesktop targeting packs.

@ryalanms ryalanms changed the title Remove new Microsoft.NETCore.App.Ref targeting pack assemblies from WindowsDesktop's targeting pack Remove new Microsoft.NETCore.App.Ref targeting pack assemblies from WindowsDesktop targeting pack Jun 17, 2021
@ryalanms ryalanms requested a review from a team June 17, 2021 19:49
@ryalanms
Copy link
Member Author

Unblocks #1746.

@RussKie
Copy link
Contributor

RussKie commented Jun 17, 2021

@dreddy-work we'll need to scan our codebase for these as well.

@ryalanms
Copy link
Member Author

Thanks, @RussKie.

@ryalanms ryalanms merged commit 50d32a9 into main Jun 17, 2021
RussKie added a commit to RussKie/winforms that referenced this pull request Jun 18, 2021
@RussKie RussKie deleted the remove.netcore.app.references.from.targeting.pack branch June 18, 2021 04:37
@@ -36,7 +36,7 @@
manually enabled by updating the metadata.
-->
<ItemGroup>
<ProjectServicingConfiguration Include="Microsoft.WindowsDesktop.App.Ref" PatchVersion="0" />
<ProjectServicingConfiguration Include="Microsoft.WindowsDesktop.App.Ref" PatchVersion="6.0.0" />
Copy link
Member

Choose a reason for hiding this comment

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

This is wrong. PatchVersion should not be the full version but just the last digit. AFAIK this setting is only relevant during servicing. @jkoritzinsky and @dagood should know more about it.

Copy link
Member

Choose a reason for hiding this comment

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

Viktor is right here.

Copy link
Member

Choose a reason for hiding this comment

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

Looks like including ("major.minor.patch".) in the comment above this group might be confusing. Intended it to just be an example of where patch version is in a full version number, but easy to interpret differently. Probably clearer just to remove it and let the rest of the comment clarify that it should normally be the same as PatchVersion.

@ViktorHofer
Copy link
Member

You are missing some of the changes that I did in the preview 6 PR: #1742. More precisely, the Version.Detail.xml and the Versions.props changes.

@ryalanms
Copy link
Member Author

Thanks, everyone. #1753.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants