Knowing ASP.NET Core 1.0 (ASP.NET 5) and why it will replace Classic ASP.NET
ASP.NET Core 1.0 - What has changed?ASP.NET Core 1.0 - Why did everything change?
You must Sign In to post a response.
Category: ASP.NET
ASP.NET Core 1.0 - Why did everything change?
#769667
ASP.NET Core is designed to be deployed on cloud as well as on-premises. Developers can now build cloud-based web applications, IoT (Internet of Thing) and mobile backend applications using ASP.NET Core framework which can run on Windows,
Linux, and Mac operating systems.
ASP.NET Core is a modular framework distributed as NuGet packages. This allows us to include packages that are required in our application
ASP.NET Core applications run on both, .NET Core and traditional .NET framework (.NET Framework 4.x).
Why ASP.NET CORE?
Supports Multiple Platforms: ASP.NET Core applications can run on Windows, Linux, and Mac. So you don't need to build different apps for different platforms using different frameworks.
Fast: ASP.NET Core no longer depends on System.Web.dll for browser-server communication. ASP.NET Core allows us to include packages which we need for our application. This reduces the request pipeline and improves the performance
and scalability.
IoC Container: It includes built-in IoC container for automatic dependency injection which makes it maintainable and testable.
Integration with Modern UI Frameworks: It allows you to use and manage modern UI frameworks such as AngularJS, ReactJS, Umber, Bootstrap etc. using Bower (a package manager for the web).
Hosting: ASP.NET Core web application can be hosted on multiple platforms with any web server such as IIS, Apache etc. It is not dependent only on IIS as a standard .NET Framework.
Code Sharing: It allows you to build a class library which can be used with other .NET frameworks such as .NET Framework 4.x or Mono. Thus a single code based can be shared across frameworks.
Side-by-Side App Versioning: ASP.NET Core runs on .NET Core which supports simultaneous running of multiple versions of applications.
Smaller Deployment Footprint: ASP.NET Core application runs on .NET Core which is smaller than full .NET Framework. So, the application which uses only a part of .NET CoreFX will have smaller deployment size. This reduces the deployment foot print
Thanks!
B.Ramana Reddy
Linux, and Mac operating systems.
ASP.NET Core is a modular framework distributed as NuGet packages. This allows us to include packages that are required in our application
ASP.NET Core applications run on both, .NET Core and traditional .NET framework (.NET Framework 4.x).
Why ASP.NET CORE?
Supports Multiple Platforms: ASP.NET Core applications can run on Windows, Linux, and Mac. So you don't need to build different apps for different platforms using different frameworks.
Fast: ASP.NET Core no longer depends on System.Web.dll for browser-server communication. ASP.NET Core allows us to include packages which we need for our application. This reduces the request pipeline and improves the performance
and scalability.
IoC Container: It includes built-in IoC container for automatic dependency injection which makes it maintainable and testable.
Integration with Modern UI Frameworks: It allows you to use and manage modern UI frameworks such as AngularJS, ReactJS, Umber, Bootstrap etc. using Bower (a package manager for the web).
Hosting: ASP.NET Core web application can be hosted on multiple platforms with any web server such as IIS, Apache etc. It is not dependent only on IIS as a standard .NET Framework.
Code Sharing: It allows you to build a class library which can be used with other .NET frameworks such as .NET Framework 4.x or Mono. Thus a single code based can be shared across frameworks.
Side-by-Side App Versioning: ASP.NET Core runs on .NET Core which supports simultaneous running of multiple versions of applications.
Smaller Deployment Footprint: ASP.NET Core application runs on .NET Core which is smaller than full .NET Framework. So, the application which uses only a part of .NET CoreFX will have smaller deployment size. This reduces the deployment foot print
Thanks!
B.Ramana Reddy
Return to Return to Discussion Forum