Skip to content

Use short component names for native files#6617

Closed
am11 wants to merge 1 commit intodotnet:masterfrom
am11:feature/native-naming
Closed

Use short component names for native files#6617
am11 wants to merge 1 commit intodotnet:masterfrom
am11:feature/native-naming

Conversation

@am11
Copy link
Member

@am11 am11 commented Nov 25, 2020

In runtime repo, property names for native files components have been unified in https://github.com/dotnet/runtime/blob/93cbc0974aa0475c586f40645e5b58a4b08ef017/eng/native/naming.props. This PR matches the naming.

@am11
Copy link
Member Author

am11 commented Nov 25, 2020

@am11
Copy link
Member Author

am11 commented Dec 8, 2020

@ViktorHofer, any thoughts on this one? 🙂

Copy link
Member

@ViktorHofer ViktorHofer left a comment

Choose a reason for hiding this comment

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

Are these properties documented to be required when consuming the SharedFramework.Sdk? This package is/will also be used by windowsdesktop and aspnetcore.

@am11
Copy link
Member Author

am11 commented Dec 8, 2020

It seems like these properties are not documented and not defined in aspnetcore repo. They are, however, defined in https://github.com/dotnet/windowsdesktop/blob/cc54c39/pkg/Directory.Build.props#L186-L216 as part of the initial port dotnet/windowsdesktop#1 from core-setup.

@ViktorHofer
Copy link
Member

@jkoritzinsky I guess only windowsdesktop uses this SDK besides dotnet/runtime currently? Are you fine with the change? Sounds like we need to react to it in dotnet/windowsdesktop.

@am11
Copy link
Member Author

am11 commented Dec 8, 2020

I can/will update windowsdesktop subsequently. :)

@am11 am11 closed this Feb 24, 2021
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.

2 participants