This repository was archived by the owner on Jan 12, 2024. It is now read-only.
Tags: NuGet/NuGet.Build.Packaging
Tags
Add the prerequisite Merq component explicitly The existing implicit prerequisite insertion from Merq nuget package isn't working as expected because the component ID in VS doesn't match the generated JSON file name, so instead of relying on the Merq.VisualStudio nuget package to inject the prerequisite, we just add it ourselves manually. Also fixed versioning of the nuget package for local builds with the new numbering scheme. Fixes #5383
Coalesce duplicate FrameworkReferences when preparing package manifes… …t. (#143) * Created test to ensure duplicate framework references are coalesced into a single reference when packaging. * Moved FrameworkAssemblyReferenceComparer from Tests to Tasks project. Added Distinct() to FrameworkReference selection in AddFrameworkAssemblies when building package manifest.
Fix package file reference when CopyToOutput=Never In this case, the package files should be referenced from their source path, not the outputpath-relative location. This was not working if the CopyToOutput was because we were only considering '' to mean "not copying", but 'Never' is also a valid value for the same situation.
Properly add Clide as a dependency (#139) When we bumped VsixDependency to properly account for VS2017 pre-requisite, we lost the plain Dependency nodes for non-component VSIXes (Clide in our case). This caused our MEF exports to not be available and the NuGet CPS exports to be missing, causing the nuproj to fall back to packages.config behavior, which doesn't work.
Add support for extending package metadata item This allows arbitrary additional metadata to be added to the package metadata item for other purpose. Fixes NuGet/Home#5387
PreviousNext