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

Fix how ClickOnce handles developement dependency package references #6037

Merged
merged 1 commit into from
Jan 15, 2021

Conversation

sujitnayak
Copy link
Contributor

Fixes #1257168

Context

Issue: ClickOnce is currently publishing contents of Nuget packages that are marked as developement dependencies. These package references should be excluded by publishing providers.

Changes Made

Filter out the development dependencies from the _DeploymentReferencePaths item group. The filtering happens by looking at the CopyToPublishDirectory attribute on ReferenceCopyLocalPaths group which is set to false for said packages.

Testing

CTI has validated specific packages that are affected and also validated the change against top 50 NuGet packages.

Notes

…ies from inclusion in the ClickOnce manifest
@rainersigwald rainersigwald changed the base branch from master to vs16.9 January 14, 2021 20:30
Copy link
Member

@rainersigwald rainersigwald left a comment

Choose a reason for hiding this comment

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

LGTM. Has someone from NuGet/super familiar with asset metadata validated this area?

@Forgind Forgind changed the base branch from vs16.9 to master January 15, 2021 16:57
@Forgind Forgind merged commit 296b367 into dotnet:master Jan 15, 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.

4 participants