IMPORTANT: Currently, changes must be backported to the in-proc branch to be included in Core Tools and non-Flex deployments.
[ ] Backporting to the in-proc branch is not required
Otherwise: Link to backporting PR
[x] My changes do not require documentation changes
[ ] Otherwise: Documentation issue linked to PR
[x] My changes should not be added to the release notes for the next release
[ ] Otherwise: I've added my notes to release_notes.md
[x] My changes do not need to be backported to a previous version
[ ] Otherwise: Backport tracked by issue/PR #issue_or_pr
[x] My changes do not require diagnostic events changes
Otherwise: I have added/updated all related diagnostic events and their documentation (Documentation issue linked to PR)
[x] I have added all required tests (Unit tests, E2E tests)
Additional information
Ever since moving to common artifact outputs, ExtensionsMetadataGenerator has been incorrectly packing itself due to hardcoding the output path format. This PR addresses that and performs further refactoring.
Assembly inclusion in the package is now done by calling into an inner-build target from the outer-build to collect all files for that TFM
ExtensionsMetadataGenerator.Console is now referenced via a ProjectReference, correctly establishing restore & build ordering.
Issue describing the changes in this PR
resolves #10651
Pull request checklist
IMPORTANT: Currently, changes must be backported to the
in-procbranch to be included in Core Tools and non-Flex deployments.in-procbranch is not requiredrelease_notes.mdAdditional information
Ever since moving to common artifact outputs, ExtensionsMetadataGenerator has been incorrectly packing itself due to hardcoding the output path format. This PR addresses that and performs further refactoring.
ExtensionsMetadataGenerator.Consoleis now referenced via aProjectReference, correctly establishing restore & build ordering.