Scribd
Upload
4 views2 pages

.NET Core vs .NET Framework Explained

.NET Standard is a specification for .NET APIs that allows code sharing across different .NET implementations, with a recommendation to target .NET Standard 2.0 for compatibility. .NET Core is cross-platform while .NET Framework is limited to Windows, and ASP.NET Core offers features like unified MVC and Web API, built-in dependency injection, and easy integration with client-side frameworks. Additionally, ASP.NET Core supports multiple environments through launchSettings.json and includes various authentication methods.

Uploaded by

sapphire.official02
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
4 views2 pages

.NET Core vs .NET Framework Explained

.NET Standard is a specification for .NET APIs that allows code sharing across different .NET implementations, with a recommendation to target .NET Standard 2.0 for compatibility. .NET Core is cross-platform while .NET Framework is limited to Windows, and ASP.NET Core offers features like unified MVC and Web API, built-in dependency injection, and easy integration with client-side frameworks. Additionally, ASP.NET Core supports multiple environments through launchSettings.json and includes various authentication methods.

Uploaded by

sapphire.official02
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

.

NET Core
What is .NET Standard?
It is a formal specification of .NET APIs that are available on
multiple .NET implementations. If you want to share code
between .NET Framework and any other .NET implementations
such as .NET Core, your library should target .NET Standard 2.0

Difference between .NET Core vs .NET Framework


1. .NET Framewok runs only on Windows whereas .NET Core
can run on any platform

Important features of [Link] Core


1. You can build and run cross-platform apps on Windows, Mac
and Linux

2. [Link] Core unifies MVC and Web API

3. Ability to host in IIS or self-host in your own process

4. Built-in Dependency Injection

5. Easy integration with client-side frameworks such as Angular

6. An Environment based configuration system

7. New light-weight and modular HTTP request pipeline

8. Built on .NET Core, which supports side-by-side app


versioning

9. Ships entirely as NuGet packages

Use multiple environments bases


[Link]
using [Link], we can create multiple for the
application with different command arguments under profiles
section

Custom middleware
AppSettings and Secrets
Authentication and Authorization
Types of Authentications
- Policy Based
- Claim Based
Reference:
[Link] & Debug Profile in [Link] Core - TekTutorialsHub

.NET Standard | Microsoft Docs

You might also like