Hired ASP.Net Developers Should Know About Important vNext Facts.pdf

Text-only Preview

Hired ASP.Net Developers Should Know About
Important vNext Facts
ASP.NET vNext is formally known as ASP.Net 5. While the particulars have been known for some
time, it is a good chance to look again at what is coming and how it will affect ASP.Net developers.
This article is designed as a background to vNext and is not specific to DNN.
Important vNext Facts that should be known: -
1. Combined application models
ASP.Net comprises of web API, SignalR, MVC and web pages into a single framework which is
collectively known as MVC 6.
• In ASP.Net MVC 6, there are views, controllers and models and it do not require System.web
anymore. No longer will MVC act similar- but- different to web API.
2. TWO CLR Versions
Generally, there are two sorts of .Net Framework i.e. the regular .Net version and the new core
common Language Runtime. The full CLR is every so often stated to as the ‘Desktop’ or ‘Full CLR’.
The CoreCLR has nothing in the Global Assembly Cache and numerous varieties can be installed
side by side on the same machine.
ASP.Net applications developed for vNext will benefit from leading the CoreCLR. This will allow
cross-platform deployment, meeker deployment models and fewer bugs from versions struggles.
But adoptions need to be made early in the project pipeline to ensure that Desktop CLR
dependencies are not included in code.
3. New Compiler
ASP.Net vNext uses the ‘Roslyn’ compiler, which is an accomplished compiler written in its own
language. Rosyln compiler technology is fast and enables true ‘edit and run’ proficiencies.
There is no requirement to compile an ASP.Net application and deploy the binaries, as you can
just deploy the code files and let it compile in place. Altering to a simpler deployment method
will change the way ASP.Net applications are developed and deployed. The ground-up rewrite of
the way that C# and VB.Net are compiled will also change the tool sets available as Roslyn
exposures detailed information about the compilation process, and cautiously allow you to
develop your own implementations.
4. Dependency Injection everywhere
Dependency Injection is now a first class .Net citizen and the decoration appears everywhere,
including MVC WebAPI and SignalR.
DI is not a new pattern, but different parts of .Net have been using different flavors for a
while. There is now an integrated model and if you are not familiar with DI, now is the time to
start learning.
5. One Simple project type
ASP.Net ventures are no longer dissimilar types like ‘Web Application Projects’ and ‘Web Site
Projects’. In fact you don’t even need a .csproj or .vbproj file for a web project. Instead, the
project is directory based and the key file is now called ‘project.json’.
Theoretically you have never needed visual studio to compile and run a project, but it was
challenging to try, with the dawn of directory-based projects and no Microsoft-specific file
formats, any decent text editor can become an ASP.Net editor.
6. Changes to the Application Pipeline
The Asp.Net pipeline has been re-invented. Understanding and manipulating the ASP.Net
pipeline was always problematic, and there was no concrete assurance that modules listed in a
web. Config file would perform in the expected order.
The traditional httpModule / httpHandler model is now a specific programming order in its
place of a set of components listed in configuration.
Source - https://www.laitkor.com/hired-asp-net-developers-should-know-
about-important-vnext-facts/