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

Don't package reference inbox assemblies on .NETCoreApp #1269

Merged
merged 2 commits into from
Jan 5, 2024

Conversation

ViktorHofer
Copy link
Member

@ViktorHofer ViktorHofer commented Jan 3, 2024

  • Microsoft.Win32.Registry got added to the .NETCoreApp shared framework with .NET 5.
  • System.Threading.Tasks.Extensions has been part of the shared framework since I believe .NET Core 2.0.
  • Microsoft.Bcl.AsyncInterfaces since .NET Core 2.1.

Don't reference these packages on .NETCoreApp to reduce the dependency graph and with that potential CVEs / CG warnings.

Microsoft.Win32.Registry got added to the .NETCoreApp shared framework with .NET 5.
System.Threading.Tasks.Extensions has been part of the shared framework since I believe .NET Core 2.0.
Microsoft.Bcl.AsyncInterfaces since .NET Core 2.1.

Don't reference these packages on .NETCoreApp to reduce the dependency graph and with that potential CVEs / CG warnings.
@AArnott
Copy link
Member

AArnott commented Jan 4, 2024

@ViktorHofer Is there any reason we should take steps to ensure this goes into 17.9? Or would 17.10 be sufficient?

@ViktorHofer
Copy link
Member Author

Responded offline as well. 17.10 is fine, there's no time pressure at all.

@AArnott AArnott added this to the v17.10 milestone Jan 5, 2024
@AArnott AArnott merged commit f5e95dd into microsoft:main Jan 5, 2024
6 checks passed
@ViktorHofer ViktorHofer deleted the patch-1 branch January 6, 2024 08:19
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