Skip to content

Conversation

@nguerrera
Copy link
Contributor

Fix #3257

There were two issues.

  1. A misunderstanding of msbuild batching rules and unqualified metadata caused satellite assemblies to be included twice (from same source location) into the publish list. (See Help understanding some batching behavior msbuild#4429)
  2. There are assemblies with the same name and version in multiple frameworks. We have to choose one arbitrarily.

@nguerrera nguerrera requested review from a team, dsplaisted, ericstj and peterhuene June 11, 2019 18:49
int cmp = string.CompareOrdinal(item1.PackageId, item2.PackageId);
if (cmp != 0)
{
return cmp < 0 ? item1 : item2;
Copy link
Contributor Author

Choose a reason for hiding this comment

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

There should probably be logging here, but I want to make a pass over all the logging in this task: see #3319

@nguerrera nguerrera merged commit 9d81590 into dotnet:master Jun 12, 2019
dsplaisted pushed a commit to dsplaisted/sdk that referenced this pull request Feb 19, 2020
…0191025.3 (dotnet#3320)

- Microsoft.AspNetCore.DeveloperCertificates.XPlat - 5.0.0-alpha1.19525.3
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.

Double write during publish

3 participants