Skip to content

Remove remarks about out of support .NET versions (System namespace)#12860

Open
gewarren wants to merge 3 commits into
dotnet:mainfrom
gewarren:netcore-set1
Open

Remove remarks about out of support .NET versions (System namespace)#12860
gewarren wants to merge 3 commits into
dotnet:mainfrom
gewarren:netcore-set1

Conversation

@gewarren

@gewarren gewarren commented Jul 7, 2026

Copy link
Copy Markdown
Collaborator

Contributes to #12648.

Updated remarks section to indicate that content is to be added.
Comment thread xml/System/Environment.xml Outdated
Comment thread xml/System/UIntPtr.xml Outdated
Comment thread xml/System/UIntPtr.xml Outdated
Comment thread xml/System/UIntPtr.xml Outdated
Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
@gewarren gewarren marked this pull request as ready for review July 7, 2026 03:51
@gewarren gewarren requested review from a team as code owners July 7, 2026 03:51
Copilot AI review requested due to automatic review settings July 7, 2026 03:51

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR updates System namespace reference docs to remove or generalize remarks that call out out-of-support .NET/.NET Core versions, aligning with issue #12648.

Changes:

  • Rephrases several remarks to remove explicit references to older .NET/.NET Core versions.
  • Simplifies or removes version-specific behavioral notes in various System API topics.
  • Updates a few links / phrasing to be version-agnostic (for example, tutorial titles and project wording).

Reviewed changes

Copilot reviewed 12 out of 12 changed files in this pull request and generated 4 comments.

Show a summary per file
File Description
xml/System/Uri.xml Rewords Unix implicit file path remark to remove “.NET Core” mention.
xml/System/UIntPtr.xml Removes explicit .NET 7 targeting qualifiers from remarks about interfaces / C# behavior.
xml/System/Type.xml Rephrases reflection-ordering remarks to remove older-version comparisons.
xml/System/TimeZoneInfo.xml Removes older-version qualifiers around IANA support and caching behavior; refines ICU-related remarks.
xml/System/String.xml Removes a table mapping Unicode versions to older .NET releases; rewords a sample-project reference.
xml/System/MarshalByRefObject.xml Generalizes obsolescence remarks without referencing .NET 5.
xml/System/IntPtr.xml Removes explicit .NET 7 targeting qualifiers from remarks about interfaces / C# behavior.
xml/System/IAsyncDisposable.xml Updates tutorial link text to remove older-version naming.
xml/System/Guid.xml Removes “starting with .NET 6” qualifier from non-Windows entropy note.
xml/System/GC.xml Removes version-specific remark in AllocateArray/AllocateUninitializedArray docs (currently replaced with a placeholder in one spot).
xml/System/Environment.xml Removes “.NET 5 and later” / “starting with .NET 6” qualifiers from remarks.
xml/System/Char.xml Removes “introduced in .NET Core 3.0” qualifier for System.Text.Rune.

Comment thread xml/System/Uri.xml
```

These implicit file paths are not compliant with the URI specification and should be avoided when possible. When using .NET Core on Unix-based systems, implicit file paths can be especially problematic, because an absolute implicit file path is *indistinguishable* from a relative path. When such ambiguity is present, <xref:System.Uri> default to interpreting the path as an absolute URI.
These implicit file paths are not compliant with the URI specification and should be avoided when possible. When using .NET on Unix-based systems, implicit file paths can be especially problematic, because an absolute implicit file path is *indistinguishable* from a relative path. When such ambiguity is present, <xref:System.Uri> default to interpreting the path as an absolute URI.
Comment thread xml/System/String.xml
## Examples

Numerous examples that call the <xref:System.String.Format*> method are interspersed throughout this article. You can also download a complete set of `String.Format` examples, which are included a [.NET Core project for C#](/samples/dotnet/samples/string-format/).
Numerous examples that call the <xref:System.String.Format*> method are interspersed throughout this article. You can also download a complete set of `String.Format` examples, which are included a [.NET project for C#](/samples/dotnet/samples/string-format/).
Comment thread xml/System/GC.xml

]]></format>
</remarks>
<remarks>To be added.</remarks>
Comment thread xml/System/GC.xml
Comment on lines 278 to 281
## Remarks

In .NET 7 and earlier versions: If pinned is set to `true`, `T` must not be a reference type or a type that contains object references.

Skipping zero-initialization is a security risk. The uninitialized array can contain invalid valuetype instances or sensitive information created by other parts of the application.
The code operating on uninitialized arrays should be heavily scrutinized to ensure that the uninitialized data is never read.
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