ASP.Net Core 2.1 web framework Explained in Detail!
Microsoft has been offering a developer pack for the beta version of .Net framework since years. The newly born ASP.Net Core 2.1 framework focuses on functional testing of MVC applications, creating a package for in-memory testing. For those who have no idea regarding ASP.Net Core, it is Microsoft’s cross-platform open source web framework that works best for.Net Core, an open-source subset of the .Net Framework.
A Nuget package popularly known as AspNetCore.Mvc.Testing is included in ASP.Net core 2.1 with which developers can now reliably test MVC applications. The package copies the .deps file from a project into a test assembly bin folder and enables static views and files to be found. The WebApplicationTestFixture<TStartup> capability is provided to bootstrap an app on TestServer.
Features included in ASP.Net Core 2.1 are:
• Improvements to Razor Pages, this provides a page based model for building a web UI. The latest version released will add immense support for areas, for portioning large MVC apps into smaller groupings. Each group has its own controllers and views. Also, Razor Pages will fall back to finding assets such as layouts in /[pages root]/Shared before reverting back to /Views/Shared.
• The ASP.Net SignalR library will be ported to ASP.Net Core for real-time web support.
• A subset of ASP.Net Webhooks, providing a lightweight pattern for web event notification, will be ported to ASP.Net Core, integrating with ASP.Net Core idioms. Receivers such as Slack and BitBucket will be ported as well.
• For security purpose, HTTPS will be on by default. Also, HTTPS redirection will direct HTTP traffic to HTTPS, via middleware that redirects based on configuration or bound server ports.
• Virtual authentication schemes must make it easier to mix authentication schemes and compose different authentication verbs across handlers.
• A default identity UI implementation is provided as a library, in order to help add identity to an application.
• The Kestrel HTTP server will be supported by a new transport based on socket types in .Net, in addition to the default libuv transport. The new socket transport could perform better than libuv.
• The Httpclientfactory type will be available to configure and consume instances of HttpClient in an application.
• Project templates will feature extension points to meet the EU’s General Data Protection Regulation (GDPR)
So that’s all for now! For more information, feel free to get in touch with a reliable .Net development company in town.
