With the RTM release of ASP.NET Core 1.0 scheduled to happen in early 2016, there's been a lot of new terminology floating around the Microsoft space. Having attended a couple of conferences recently has helped me sort them out a bit, but some of them are still quite confusing. What's Bower and NPM, and why do I need them? Why does everyone keep talking about Roslyn?
I can't be the only one with this issue, so below is a glossary which includes a list of terms and codenames and definitions for such that I've compile. All of these terms relate in one way or another to ASP.NET Core 1.0, ASP.NET 4.6, and their constituent technologies. If I left anything out, please feel free to
yell at me kindly tell me so in the comments!
The ASP.NET Core 1.0 Glossary
ASP.NET 5: The project that is now known as ASP.NET Core 1.0.
docs.asp.net: The open-source, community-driven documentation for ASP.NET 4.6, ASP.NET Core 1.0, OWIN, Kestrel, DNX, Katana, Roslyn, and many other components of the .NET Framework.
.NET 4.6: The full functionality of the .NET Framework, contrasted with .NET Core. Is now being developed on a separate track, and will include support for WebForms (but is not open-source and cannot be deployed to Mac or Linux).
.NET Core 1.0: A small, optimized runtime that represents a ground-up rewrite of the .NET framework. Designed to be modular and includes a subset of the full .NET functionality (for example, .NET Core 1.0 does not include WebForms or System.Drawing).
Dependency Injection (DI): A software development best-practice that implements inversion of control, used to resolve dependencies. DI is now supported natively by ASP.NET Core 1.0 projects via the use of the Startup.cs file. See also the ASP.NET Core 1.0 Docs.
DNVM: .NET Version Manager. An open-source manager that allows developers to download and install multiple versions of the .NET Runtimes.
DNX: .NET Execution Environment. An open-source environment which includes the code necessary to bootstrap and run an ASP.NET Core 1.0 application.
Katana: A codename for open-source OWIN components built and released by Microsoft. Katana also enables developers to develop a Web application using a wide range of technologies and then host that app wherever they desire. See Howard Dierking's article and Mike Wasson's Getting Started with OWIN and Katana.
Middleware: A term for components that form a pipeline between server and client. Middleware inspects, modifies, or routes request and response messages for a specific purpose. Middleware effectively replaces HttpModules in ASP.NET Core 1.0. This concept was popularized in the .NET space by the OWIN project. See Mike's Dot Netting or the ASP.NET docs.
Project K: The original code name for the project that became .NET Framework Core 1.0
Roslyn: The open-source compiler for .NET Core 1.0 and .NET 4.6, developed and maintained by Microsoft.
OWIN: Open Web Interface for .NET. A project whose goal is to create standard interfaces between .NET web servers and web applications, thereby breaking the tight coupling between ASP.NET and IIS. Implementing the standards defined by this project into ASP.NET Core 1.0 projects allows the creation of Middleware. See An Overview of Project Katana (which contains a good high-level summary of OWIN).
Startup.cs: A file included in all ASP.NET Core 1.0 projects that, among other things, adds services to the Dependency Injection layer and constructs the pipeline used by the DNX environment for that app.
Task Runner: General term for a tool that automates certain tasks, such as bundling or minification of client-side resources. Gulp and Grunt are both task runners. Visual Studio supports task runners in the Task Runner Explorer window.
Yeoman: An open-source project scaffolding tool that generates complete, run-able projects for a given set of tools, similar to a Visual Studio project template. Commonly-used in Mac or Linux environments for ASP.NET Core 1.0 applications.
NOTE (1/21/2016): This article has
been updated to reflect the renaming of ASP.NET 5 to ASP.NET Core 1.0