Skip to content
This repository has been archived by the owner on Sep 13, 2022. It is now read-only.

Use a file list rather than globbing NETStandard assemblies #507

Merged
merged 1 commit into from
Sep 25, 2017

Conversation

ericstj
Copy link
Member

@ericstj ericstj commented Sep 22, 2017

This change minimizes the amount of work done during project evaluation by directly
setting the reference items to all the files/paths we know are part of the package.

/cc @weshaggard @davkean

#442

This change minimizes the amount of work done during project evaluation by directly
setting the reference items to all the files/paths we know are part of the package.
<NuGetPackageId>NETStandard.Library</NuGetPackageId>
<NuGetPackageVersion>$(NETStandardLibraryPackageVersion)</NuGetPackageVersion>
</Reference>
<Reference Include="#NETSTANDARDFACADES#">
Copy link
Member

Choose a reason for hiding this comment

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

That is going to turn into a pretty long include string. Are there any limits in the length of that over just having one item per facade?

Copy link
Member Author

Choose a reason for hiding this comment

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

Not that I am aware of. MSBuild is using managed code to parse this thing so its not like we impose any limits on strings in a file. I'm trying to keep the overall text size down as well because I don't want to increase the file size/parsing by a ton.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants