Skip to content

Set PrivateAssets to "all" on the X509Certificates references#9380

Merged
MattGal merged 1 commit intorelease/6.0from
cg-x509-changes
May 17, 2022
Merged

Set PrivateAssets to "all" on the X509Certificates references#9380
MattGal merged 1 commit intorelease/6.0from
cg-x509-changes

Conversation

@MattGal
Copy link
Copy Markdown
Member

@MattGal MattGal commented May 16, 2022

This should prevent bringing this dependency to indirect references of arcade packages. @ericstj FYI.

To double check:

…nt bringing this dependency to indirect references of this package.
@ericstj ericstj requested review from a team, ViktorHofer and hoyosjs May 17, 2022 14:02
<!-- Don't let it restore lower versions of this package, which can come transitively from NetStandard package restores (CSProj only) -->
<ItemGroup Condition="'$(MSBuildProjectExtension)' == '.csproj'" >
<PackageReference Include="System.Security.Cryptography.X509Certificates" Version="$(SystemSecurityCryptographyX509CertificatesVersion)" />
<PackageReference Include="System.Security.Cryptography.X509Certificates" Version="$(SystemSecurityCryptographyX509CertificatesVersion)" PrivateAssets="All" />
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This should be OK as a low risk fix to get things flowing.

Ideally no project should be bringing in packages from .NETCore 1.1 in our builds for .NET 7.0. We should try to drive these out over time. Probably first in main, only backporting things that are low-risk enough for servicing.

@MattGal MattGal merged commit 33d9d99 into release/6.0 May 17, 2022
@akoeplinger akoeplinger deleted the cg-x509-changes branch May 24, 2022 18:37
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.

2 participants