Skip to content
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

Updates from MSBuild 17.x and NuGet 6.x #30

Draft
wants to merge 4 commits into
base: develop
Choose a base branch
from
Draft

Conversation

Nirmal4G
Copy link
Contributor

@Nirmal4G Nirmal4G commented Jun 26, 2022

Updates from MSBuild repository

  • Produce reference assembly in new ref output folder

Updates from NuGet repository

  • Check and De-Duplicate NuGet Items
  • Prefer TargetFramework when specified globally

Previously, we were producing the reference assembly in the `OutputPath` directory.
But we also want to produce the reference assembly in a folder `ref` beside `bin` folder.

With that, introduce `ProduceReferenceAssemblyInOutputPath` to control output directory preference;
the `BaseReferenceOutputPath` and `ReferenceOutputPath` as the goto destination for reference assemblies!
- Check, Warn and De-Duplicate NuGet Items
  This applies to `PackageReference`, `PackageVersion` and `PackageDownload` item types.
- Allow overrides for properties such as
  1. `ManagePackageVersionsCentrally`
  2. `RestoreEnableGlobalPackageReference`
  3. `DisableCheckingDuplicatePackage(Download|Reference|Version)s`
- Prefer "TargetFramework" over its plural counterpart
  when specified globally, like on the command-line
  and in the MSBuild task, Properties metadata.

- This also adds a "GetGlobalPropertyValueTask" for getting global properties.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant