the lesser scotts
[WHAT]
- ] This ia a SUMMARY of a VIDEO Q+A session at the 2015 microsoft build developer conference. Panel consisting of Scott Hanselman, Scott Hunter, Damien Edwards (ASP.net) and Rowan __ (EF guy)
[WHY]
- ] SUMMARY of a VIDEO
[WHERE]
- ] WATCH THE FULL VIDEO
- ] The lesser scotts
[WHEN]
- ] 2015-05-01
[EXAMPLE]
- ] what is '.net framework'?
- ] when you compile your app, you compile against a set of assemblies
- ] you then add references, call apis within those references
- ] previously introduced concept of reference assemblies(contracts), they represent the platform that you want to compile against, ex silverlight, windows phone,
- ] where ever ".net" is running
- ] example - when your in vs, your not running on windows phone, your compiling against a set of 'reference assemblies' that represent that platform
- ] .net framework has a set of reference assemblies that represent the .dot net framework on windows
- ] .net client profile (from ver 4 ) also had a set of those as well
- ] now that we have ] .net core ] .dnx ] .asp core
- ] > your always going to be 'compiling against' a 'promise' of 'what your going to be runinng on'
- ] portable class libraries
- ?] a common subset of reference assemblies
- ] the new 'asp.net' - is it new, are we starting over,
- ] its a brand new thing that looks a lot like the old thing, it is "concept compatible"
- ] there still are /controllers, /views, /routes, /actions, /razor,
- ] BUT IF you go deep down the stack, there is NO system.web
- ] EXAMPLE - of going from a 'regular car' to a 'hybrid car', the mechanics have changed, but the car still drives the same
- ] can bring in resources you need, open source taskrunners, javascript libraries,
- ] its still .net, .net on system.web(as we know it now), .net on windows phone, .net on window, its all .net
- ] .net represents a lot of different things ( )
- ] modularity
- ] what are the MAIN benefits of the "new" .net
- ] benefit = the ability to run multiple .net vers side-by-side on 1 server, with different versions of .net on server
- PRB cust develops app for 1 .net ver but server has different .net ver, cust afraid to add new/diff .net vers to server b/c of existing .net ver on server, doesnt want to risk breaker
- ] benefits = x/platform - .net apps can now be run ON linux, windows, azure web services and mac platforms
- ] - app user process
- ] example - demo in .net deep dive presentation - published a .net app to a usb stick, choosing a random laptop from audience member, .net app works w/out touching anything on the laptop, no registry, no system 32
- ] .net framework - ships with windows,
- ] NEW .net core -
- ] asp.net 5 can target either .net core or .net framework
- *] there are implications to your choices, .net core is 11MB, frameworks is 100MB+, it doesnt have all the same stuff
- ]
- [07:30] what about Entity Framework 7.x ()
- - concept compatible -
? asp.net or php
- web api, mvc, singleR, web pages (EX mads kristensen )
- vs OR vs code
? katana owin and asp.net 5
-
> 2 sessions 2 watch for primer
dnx - execution manager
dnv - version manager
dnu - utilites
? performance
? gulp or grunt
- runtime, bundling, minification
- default framework
- lots of choices
- user has to think about whats
? will asp.net run on iis7
- no 7.5 >
? will asp.net identity be changing
-
? more ways for developer to tap into the pipeline
- helios
-
? will migration help
be available
- guidance
- no tools for upgrade from mvc5 to mvc6
* more open, more choice ,
[HOW-TO]
- ] jeffry snowmer
[REFERENCE]
- ] VIDEO http://channel9.msdn.com/Events/Build/2015/C9-16
<iframe src="//channel9.msdn.com/Events/Build/2015/C9-16/player" width="560" height="315" allowFullScreen frameBorder="0"></iframe>