Glossary updates #38103
Glossary updates #38103
Conversation
…ide-by-side view editors easier.
|
@SamuelEnglard what is the status of this PR? |
|
@danmosemsft distracted by work so haven't had time to work on it. Hoping to have time next week, |
| * **CoreFX**. Core framework. Conceptually a set of `System.*` (and to a limited | ||
| extent `Microsoft.*`) libraries that make up the lower layer of the .NET | ||
| library stack. It's what most people would think of as the Base Class Library | ||
| (BCL). The BCL is a general purpose, lower level set of functionality that |
There was a problem hiding this comment.
Actually it's now more than the BCL (if the BCL concretely means, the "shared framework" otherwise known as Microsoft.NetCore.App, which is the set of types automatically referenced by all .NET Core apps). For example, CoreFX also contains the types in the Windows Compatibility pack.
|
|
||
| It's built from the same code base as the CLR. Originally, CoreCLR was the | ||
| runtime of Silverlight and was designed to run on multiple platforms, | ||
| specifically Windows and OS X. CoreCLR is now part of .NET Core and represents a |
|
|
||
| That's why referring to .NET Core as 'Store' is no longer correct. But you can think of today's .NET Core as an evolution of the original APIs available for store applications. Many of the original design goals are still relevant, especially around layering and portability. | ||
| That's why referring to .NET Core as 'Store' is no longer correct. But you can |
There was a problem hiding this comment.
I think it is not worth making any connection between .NET Core and "Store" anymore
| source][Newtonsoft.Json] and support almost every platform .NET code can run on | ||
| (.NET Framework 2.0, 3.0, 3.5, 4.0, and 4.5; Mono; MonoTouch/Xamarin.iOS; | ||
| MonoDroid/Xamarin.Android; Silverlight 3, 4, and 5; Windows Phone 8, 8, and 8.1; | ||
| Windows 8 Store; .NET Core). |
There was a problem hiding this comment.
In .NET Core 3.0, an all new JSON API will be built into the .NET Core shared framework: System.Text.Json. It is particularly optimized for performance.
There was a problem hiding this comment.
Should I mention that it's replaced or remove mention at all?
|
Can you explain why you manually wrapped? That seems strictly worse as if I shrink my window (or use a popular extension to widen the github display) it does not wrap correctly. |
|
@SamuelEnglard thanks for this PR. I see it has been inactive for about a month. |
|
@maryamariyan I can't think of any more changes right now, so I'll change it to a non-draft PR. |
|
thanks @SamuelEnglard |
Remove unused markdown definitions introduced in dotnet/corefx#38103
* Update glossary.md Remove unused markdown definitions introduced in dotnet/corefx#38103 * Update source-generator-pinvokes.md Remove unused markdown definitions introduced in #33742
* Update glossary.md Remove unused markdown definitions introduced in dotnet/corefx#38103 * Update source-generator-pinvokes.md Remove unused markdown definitions introduced in dotnet/runtime#33742
* Changed links in glossary to use footnote style, makes reading markdown easier * Change glossary to have no lines over 80 characters. Makes using in side-by-side view editors easier. * Added section on CLI * Moved runtimes from terms to their own section, and fixed a missing formating * Corrected typo with second meaning of CLI * Added note about CLI also refering to .NET tooling * Removed WPF alternatives and added information about OSS of WPF and WinForms * Formatting cleaning up for glossary and added missing AKAs * Update glossary.md Commit migrated from dotnet/corefx@c575d08
This is NOT ready to merge but wanted to start talking about it.
/cc: @terrajobst