Add .NET Components article #1232
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,81 @@ | ||
| --- | ||
| title: .NET Architectural Components | ||
| description: Describes key .NET architectural components such as the .NET Standard Library, .NET runtimes, and tooling. | ||
| keywords: .NET, .NET Standard Library, .NET Standard, .NET Core, .NET Framework, Xamarin, MSBuild, C#, F#, VB, compilers | ||
| author: cartermp | ||
| manager: wpickett | ||
| ms.author: cartermp | ||
| ms.date: 11/16/2016 | ||
| ms.topic: article | ||
| ms.prod: .net | ||
| ms.technology: .net-core-technologies | ||
| ms.devlang: dotnet | ||
| ms.assetid: 2e38e9d9-8284-46ee-a15f-199adc4f26f4 | ||
| --- | ||
|
|
||
| # .NET Architectural Components | ||
|
|
||
| .NET is made up of a number of key components. It has a standard library, called the .NET Standard Library, which is a large set of APIs which runs everywhere. This standard library is implemented by three .NET runtimes - .NET Framework, .NET Core, and Mono for Xamarin. The .NET languages also run on any .NET runtime. Additionally, there are tools on every platform which allow you to build projects. These tools are the same regardless of your choice of runtime. | ||
|
|
||
| Here's a graphical overview of each of the previously mentioned components of .NET and how they fit. | ||
|
|
||
|  | ||
|
|
||
| What follows is a brief explanation of each of the key components shown above. | ||
|
|
||
| ## .NET Standard Library | ||
|
|
||
| The .NET Standard Library is a set of APIs which are implemented by a .NET runtime. | ||
|
|
||
| More formally, it is a specification of .NET APIs which make up a uniform set of contracts that you compile your code against. These contracts have underlying implementations for each .NET runtime. This enables portability across different .NET runtimes, making it so that your code can effectively "run everywhere". | ||
|
|
||
| The .NET Standard Library is also a build target, where it is known as the .NET Standard. You can currently target .NET Standard 1.0-1.6. If your code targets a version of the .NET Standard, it is guaranteed to run on any .NET runtime which implements that version. | ||
|
|
||
| To learn more about the .NET Standard library and targeting the .NET Standard, see [.NET Standard Library](library.md). | ||
|
|
||
| ## .NET runtimes | ||
|
|
||
| There are 3 primary .NET runtimes which Microsoft actively develops and maintains: .NET Core, .NET Framework, and Mono for Xamarin. | ||
|
|
||
| ### .NET Core | ||
|
|
||
| .NET Core is a cross-platform runtime optimized for server workloads. It implements the .NET Standard Library, which means that any code that targets the .NET Standard can run on .NET Core. It is the runtime used by ASP.NET Core and the Universal Windows Platform (UWP). It is modern, efficient, and designed to handle server and cloud workloads at scale. | ||
|
There was a problem hiding this comment. we don't distinguish between Core and Native? There was a problem hiding this comment. Not at this stage, no. .NET Native is changing enough to the point where we're just sticking with this for now. The short of it is that UWP is a .NET Core-based stack which brings along other APIs. |
||
|
|
||
| To learn more about .NET Core, see the [.NET Core Guide](../core/index.md). | ||
|
|
||
| ### .NET Framework | ||
|
|
||
| .NET Framework is the historical .NET runtime that has existed since 2002. It is the same .NET Framework existing .NET developers have always used. It implements the .NET Standard Library, which means that any code that targets the .NET Standard can run on the .NET Framework. It contains additional Windows-specific APIs, such as APIs for Windows desktop development with Windows Forms and WPF. .NET Framework is optimized for building Windows desktop applications. | ||
|
|
||
| To learn more about the .NET Framework, see the [.NET Framework Guide](../framework/index.md). | ||
|
|
||
| ### Mono for Xamarin | ||
|
|
||
| Mono is the runtime used by Xamarin apps. It implements the .NET Standard Library, which means that any code that targets the .NET Standard can run on Xamarin apps. It contains additional APIs for iOS, Android, Xamarin.Forms, and Xamarin.Mac. It is optimized for building mobile applications on iOS and Android. | ||
|
|
||
| To learn more about Mono, see the [Mono documentation](http://www.mono-project.com/docs/). | ||
|
|
||
| ## .NET tooling and common infrastructure | ||
|
|
||
| Tooling for .NET is also common across each implementation of .NET. These include, but are not limited to: | ||
|
|
||
| * The .NET languages and their compilers | ||
|
There was a problem hiding this comment. these items should end with a period. |
||
| * Runtime components, such as the JIT and Garbage Collector | ||
| * .NET project system (sometimes known as "csproj", "vbproj", or "fsproj") | ||
| * MSBuild, the build engine used to build projects | ||
| * NuGet, Microsoft's package manager for .NET | ||
| * The .NET CLI, a cross-platform command-line interface for building .NET projects | ||
| * Open Source build orchestration tools, such as CAKE and FAKE | ||
|
|
||
| The main takeaway here should be that there is a vast amount of tooling and infrastructure which is common for any "flavor" of .NET you choose to build your apps with. | ||
|
|
||
| ## Next Steps | ||
|
|
||
| To learn more, visit the following: | ||
|
|
||
| * [.NET Standard Library](library.md) | ||
| * [.NET Core Guide](../core/index.md) | ||
| * [.NET Framework Guide](../framework/index.md) | ||
| * [C# Guide](../csharp/index.md) | ||
| * [F# Guide](../csharp/index.md) | ||
| * [VB.NET Guide](../csharp/index.md) | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we're also adding ms.author which is the person who is going to be responsible for maintain and receive feedback bugs, BI data, etc.