ASP.NET 5: How to Get Your Cheese Back
Presenter Tugberk Ugurlu
Surprised by how much has been changed in ASP.net 5. I think the changes are good, but concerned about lack of backward compatibility. MVC is now free of system.web so can be deployed sans IIS.
- ASP.net 5 is entire rewrite
- All files are part of project have to exclude what don’t want
- Unified dependencies
- can set dependency by framework
- Project file is not .json
- Configure method in startup, similar to owin and katana
- New concepts
- Command line tools
- dnvm: dot net version manager
- manages the versions of .net on your machine
- Can assign different framework version to different processes running at same time
- dnx: dot net execution environment
- dnx run will run your application
- dnu: dot net utility
- dnvm: dot net version manager
- Command-line first development ?
- Command line tools
- Modular, Composable HTTP Pipelie
- pipeline is entirely empty to start have to add everything
- good since don’t have to pay the price for things you don’t use.
- in startup configure method you add to the pipepline what you want
- pipeline is entirely empty to start have to add everything
- Dependency injection all the way down
- built in container get swap out with your favorite
- ConfigureServices method in stratup used to config DI
- ConfigureOptions<T>, syntax for configuring, like identity
- Config
- in startup you tell app where and what kind of config files exist
- configurationmanager is all gone, where it was used you need to change
- Unified mvc and webapi
- removed mvc dependency on system.web
- Code editor agnostic
- Cross platform now
- can run windows,linux, osX
- kestrel web server is supported
- Can be dockerized now