Last summer, when ASP.NET 5 was at beta 4, I took a look and liked what I saw. This is a lean, fast, cross-platform framework, and it gives us more control over the request processing pipeline than we’ve had before.
Fast-forward to October. ASP.NET 5 was nearing beta 8, but I had been busy with work and wasn’t keeping up with the beta releases. Fortunately, I had a few weeks with a bit more free time, so I gave myself a project to focus on: rebuild the Contoso University sample using ASP.NET 5. Working nights and weekends, I was able to complete the project (and write-up documentation for Sake), but I didn’t have time to focus on certain aspects of ASP.NET 5, like configuration or identity.
So this will be my project for the start of 2016: as ASP.NET 5 heads to a 1.0.0 release by the end of March, I’ll be looking at specific areas of the framework and writing up posts that take a very “how to” approach to the topics under discussion. Each post will include source code for projects that are as simple as possible to focus on the topic. I plan to have both Visual Studio 2015 projects and command line projects that will run on both Windows and Linux.
To follow along with the examples, you will need to install ASP.NET 5, which is currently at version 1.0.0-rc1-update1. Here are a few tips/gotchas:
- If you want to run ASP.NET 5 on Ubuntu, only version 14.04 is supported.
- In order to run dnvm on Windows, you must allow execution of remote signed scripts.
- If you use PowerShell and navigate to a project folder using the wrong case,
dnu restorewill return an error saying it is “Unable to locate Dependency {incorrectly cased project directory name}”. For those new to PowerShell, tab completion is your friend here.
Roadmap
(subject to change)
- Cross-cutting Concerns
- Configuration
- Dependency Injection
- User Secrets
- Logging
- Diagnostics
- Identity
- Localization
- Entity Framework 7 (details TBD)
- MVC 6 (details TBD)
[…] Exploring ASP.NET 5 […]