Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Landing page - explain full .NET Framework. #5571

Merged
merged 2 commits into from
Mar 3, 2018
Merged

Landing page - explain full .NET Framework. #5571

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a2e2b1c
Landing page - explain full .NET Framework.
Rick-Anderson Mar 1, 2018
02bc8a1
.NET Framework target framework patches (#5573)
scottaddie Mar 1, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 15 additions & 2 deletions aspnetcore/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ ASP.NET Core provides the following benefits:
* Ability to build and run on Windows, macOS, and Linux.
* Open-source and [community-focused](https://live.asp.net/).

ASP.NET Core ships entirely as [NuGet](https://www.nuget.org/) packages. This allows you to optimize your app to include only the necessary NuGet packages. In fact, ASP.NET Core 2.x apps targeting .NET Core only require a [single NuGet package](xref:fundamentals/metapackage). The benefits of a smaller app surface area include tighter security, reduced servicing, and improved performance.
ASP.NET Core ships entirely as [NuGet](https://www.nuget.org/) packages. Using NuGet packages allows you to optimize your app to include only the necessary NuGet packages. In fact, ASP.NET Core 2.x apps targeting .NET Core only require a [single NuGet package](xref:fundamentals/metapackage). The benefits of a smaller app surface area include tighter security, reduced servicing, and improved performance.
Copy link
Member

Choose a reason for hiding this comment

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

Let's keep an eye on this 3rd sentence. ASP.NET Core 2.1 may introduce metapackage support for apps targeting .NET Framework as well. See aspnet/MetaPackages#255 (comment).


## Build web APIs and web UI using ASP.NET Core MVC

Expand All @@ -54,7 +54,20 @@ ASP.NET Core MVC provides features to build [web APIs](xref:tutorials/index#buil

## Client-side development

ASP.NET Core integrates seamlessly with popular client-side frameworks and libraries, including [Angular](xref:spa/angular), [React](xref:spa/react), and [Bootstrap](xref:client-side/bootstrap). See [Client-side development](xref:client-side/index) for more details.
ASP.NET Core integrates seamlessly with popular client-side frameworks and libraries, including [Angular](xref:spa/angular), [React](xref:spa/react), and [Bootstrap](xref:client-side/bootstrap). For more information, see [Client-side development](xref:client-side/index).

## ASP.NET Core on the .NET Framework

ASP.NET Core can target .NET Core or the .NET Framework. ASP.NET Core apps targeting the .NET Framework are cross-platform. There are no plans to remove support for running on the .NET Framework from ASP.NET Core. Generally, ASP.NET Core is made up of .NET Standard 2.0 libraries. Apps written with .NET Standard 2.0 should run anywhere that .NET Standard 2.0 is supported.

There are several advantages to running on .NET Core, and these advantages increase with each release. Some advantages of .NET Core over .NET Framework include:

* Cross platform. Runs on MacOS, Linux, and Windows.
* Frequently better performance.
* Side-by-side versioning.
* New APIs.

We're working hard to close the API gap from .NET Framework to .NET Core. The [Windows Compatibility Pack](https://blogs.msdn.microsoft.com/dotnet/2017/11/16/announcing-the-windows-compatibility-pack-for-net-core/) made thousands of APIs available on .NET Core that were not available in .NET Core 1.x.

## Next steps

Expand Down