Replace .NET Framework with .NET where applicable #20025
Conversation
Change newer to higher on versions for consistency
|
|
| @@ -1,13 +1,13 @@ | |||
| --- | |||
| title: "Introduction to the C# Language and the .NET Framework" | |||
| title: "Introduction to the C# Language and .NET" | |||
There was a problem hiding this comment.
This article needs to be reviewed carefully to make sure the information provided in it are not .NET Framework-specific. Then it may be worth renaming the file and adding a redirection.
There was a problem hiding this comment.
@BillWagner This is an ancient intro to C#. My inclination is to retire it and redirect to the new Tour of C#. What do you think?
There was a problem hiding this comment.
Yes, that's on my plan for part of this release cycle (probably next month).
BillWagner
added
the
✨ 1st-time docs contributor!
|
I requested an additional review from @tdykstra He's been maintaining our glossary, and it would be good to have him give this a close look 🔎 |
There was a problem hiding this comment.
In some cases, especially in link text when linking to a doc that (still) has Framework-specific content, dropping "Framework" after ".NET" could be misleading. Within docs that have Framework-specific content, dropping "Framework" is usually not as likely to result in misunderstanding. It's not always obvious what is the best choice in each instance, but I made some suggestions where I thought Framework should remain.
| @@ -1,13 +1,13 @@ | |||
| --- | |||
| title: "Introduction to the C# Language and the .NET Framework" | |||
| title: "Introduction to the C# Language and .NET" | |||
There was a problem hiding this comment.
@BillWagner This is an ancient intro to C#. My inclination is to retire it and redirect to the new Tour of C#. What do you think?
| - You passed a variable name to the [typeof](../operators/type-testing-and-cast.md#typeof-operator) operator. | ||
|
|
||
| - You tried to reference an assembly that is not part of your target .NET Framework profile. For more information, see [Troubleshooting .NET Framework Targeting Errors](/visualstudio/msbuild/troubleshooting-dotnet-framework-targeting-errors). | ||
| - You tried to reference an assembly that is not part of your target .NET profile. For more information, see [Troubleshooting .NET Targeting Errors](/visualstudio/msbuild/troubleshooting-dotnet-framework-targeting-errors). |
There was a problem hiding this comment.
The content of the referenced doc is Framework-specific.
| - You tried to reference an assembly that is not part of your target .NET profile. For more information, see [Troubleshooting .NET Targeting Errors](/visualstudio/msbuild/troubleshooting-dotnet-framework-targeting-errors). | |
| - You tried to reference an assembly that is not part of your target .NET Framework profile. For more information, see [Troubleshooting .NET Framework Targeting Errors](/visualstudio/msbuild/troubleshooting-dotnet-framework-targeting-errors). |
docs/csharp/language-reference/compiler-options/noconfig-compiler-option.md
Outdated
Show resolved
Hide resolved
docs/csharp/language-reference/compiler-options/platform-compiler-option.md
Outdated
Show resolved
Hide resolved
docs/csharp/programming-guide/concepts/expression-trees/index.md
Outdated
Show resolved
Hide resolved
docs/csharp/programming-guide/interop/how-to-access-office-onterop-objects.md
Outdated
Show resolved
Hide resolved
docs/csharp/programming-guide/interop/walkthrough-office-programming.md
Outdated
Show resolved
Hide resolved
docs/csharp/programming-guide/statements-expressions-operators/anonymous-functions.md
Outdated
Show resolved
Hide resolved
| displayName: get started | ||
| href: getting-started/index.md | ||
| - name: Introduction to the C# language and the .NET framework | ||
| - name: Introduction to the C# language and .NET |
There was a problem hiding this comment.
Another link to the old C# intro that I propose we retire.
The new term is "target framework moniker" Co-authored-by: Bill Wagner <[email protected]>
Co-authored-by: Tom Dykstra <[email protected]>
|
Is there anything pending on this for the pull or just long term planning? |
|
It should be ready to go, after merge conflicts are resolved. |
6 participants
Summary
Following the same thought and changes from pull request #18691 updated the use of .NET Framework to just .NET anywhere that wasn't explicitly referencing the Framework itself or a comparison to .Net Core. Additionally updated several references to "framework version x.x or newer" to say "framework version x.x or higher" to be consistent with other places this is used.
Contributes To #18697