Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to Safari
With ASP.NET Core you can build web apps, web services, IoT apps, and mobile backends. It can be used with Visual Studio, or with Visual Studio Code.
See article on Medium Getting started with ASP .NET Core.
Also see Tutorial: Create a web API with ASP.NET Core MVC and An awesome guide on how to build RESTful APIs with ASP.NET Core.
.NET 6 simplifies API creation with the Minimal API.
SpecsUpdate
Pros
Pro Great developer experience
Tooling is excellent. All can be done within Visual Studio; coding, testing, debugging, version control, deployment, etc.
Pro Built-in middleware
Built-in middleware featuring: Authentication, Cookie policy, Health Check, MVC, Session etc.
Pro Hosting
Ability to host on IIS, Nginx, Apache, Docker, or self-host in your own process. Also in the cloud with Azure.
Pro Managed dependency injection
Register your service layers at startup and automatically receive them in your constructor.
Pro Tooling
Both VS and VSCode are powerful free IDEs that are well integrated with ASP.net Core. VS Community also allows for commercial use for projects with less than 5 developers.
Pro JSON optimization
In .NET Core 2.1 and 3.0, new APIs are added that make it possible to write JSON APIs that require less memory, using Span<T> and UTF8 strings, and improve throughput of applications like Kestrel, ASP.NET Core web server. See also Utf8JsonReader.
Pro Built in Dependency Injection
Where in the old ASP.NET we had to rely on 3rd-party solutions, Dependency Injection is now built in.
Read Implementing an Effective Architecture for ASP.NET Core Web API.
Pro Tutorials and documentation quality
Both microsoft and 3rd party tutorials are mostly of high quality and encourage you to use the industry best-practices.
Pro No encapsulated environment
In .net framework 3.1, you can deploy the app in any platform whitout having to install the framework itself (self-contained app).
Cons
Con Unnecessarily complex
Performing basic implementations requires excessive boilerplate code. Some key stacks are poorly implemented (System.Text.Json) and do not offer enough features.
Recommendations
Comments
Flagged Pros + Cons
