Skip to content

clean up conditional compilation for now-removed TFMs#7415

Open
fowl2 wants to merge 1 commit into
NuGet:devfrom
fowl2:removeOldConditionalCompilation
Open

clean up conditional compilation for now-removed TFMs#7415
fowl2 wants to merge 1 commit into
NuGet:devfrom
fowl2:removeOldConditionalCompilation

Conversation

@fowl2
Copy link
Copy Markdown

@fowl2 fowl2 commented May 26, 2026

Since NuGet now only builds for net472 and net8.0, we can remove all the .NET Standard and previous workarounds.

@fowl2 fowl2 requested a review from a team as a code owner May 26, 2026 11:54
@fowl2 fowl2 requested review from donnie-msft and jeffkl May 26, 2026 11:54
@dotnet-policy-service dotnet-policy-service Bot added the Community PRs created by someone not in the NuGet team label May 26, 2026
Copy link
Copy Markdown
Member

@nkolev92 nkolev92 left a comment

Choose a reason for hiding this comment

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

Thanks for the contribution.
It'd be great to follow the PR template, because it actually guides you to the information we need to more effectively review the PR.

// Licensed to the .NET Foundation under one or more agreements.
// The .NET Foundation licenses this file to you under the MIT license.

#if !NETSTANDARD2_1 && !NETCOREAPP3_1_OR_GREATER && !NET5_0_OR_GREATER
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.

We still have 1 project that targets NS2.0 (NuGet.VisualStudio.Contracts), so in case we want to enable nullability there we should keep the NS2.0 support in this file.


private static void CopyTo(Stream inputStream, Stream outputStream)
{
// .NET Framework allocates an unavoidable byte[] when using
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 seems to suggest it shouldn't be removed.
This seems like a significant decision, so we either need this reverted, or explained why it's unnecessary.

Either way I would've loved to see this called out in the PR description to help the reviewer.

@nkolev92 nkolev92 added the Engineering Changes related to the build infrastructure of the repo and that do not change product code label May 26, 2026
@jebriede jebriede self-assigned this May 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Community PRs created by someone not in the NuGet team Engineering Changes related to the build infrastructure of the repo and that do not change product code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants