edit-article

Article Name:

Article Description:

Chapter ID/Name:

Status:

Add Photo:

Owner ID:

Content: use HTML Edit Content

<h1 style="text-align: center;">the lesser scotts</h1>
<h2>[WHAT]</h2>
<ol>
<li>]&nbsp;This ia a SUMMARY of a&nbsp;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)</li>
</ol>
<h2>[WHY]</h2>
<ol>
<li>]&nbsp;SUMMARY of a VIDEO</li>
</ol>
<h2>[WHERE]</h2>
<ol>
<li>] WATCH THE FULL VIDEO</li>
<ol>
<li>] <a href="http://channel9.msdn.com/Events/Build/2015/C9-16" target="_blank">The lesser scotts</a>&nbsp;</li>
</ol></ol>
<h2>[WHEN]</h2>
<ol>
<li>] 2015-05-01</li>
</ol>
<h2>[EXAMPLE]</h2>
<ol>
<li>] what is '.net framework'?</li>
<ol>
<li>] when you compile your app, you compile&nbsp;against a set of assemblies</li>
<li>] you then add references, call apis within those references</li>
<li>] previously introduced&nbsp;concept of reference assemblies(contracts), they represent the platform that you want to compile against, ex silverlight, windows phone,</li>
<li>] where ever ".net" is running </li>
<li>] example - when your in vs, your not running on windows phone, your compiling against a set of 'reference assemblies' that represent that platform</li>
<li>] .net framework has a set of reference assemblies that represent the .dot net framework on windows</li>
<li>] .net client profile (from ver 4 ) also had a set of those as well</li>
<li>] now that we have ] .net core ] .dnx ] .asp core&nbsp;&nbsp;</li>
<li>] &gt;&nbsp;your always going to be 'compiling against' a 'promise' of 'what your going to be runinng on'</li>
<li>] portable class libraries</li>
<li>?]&nbsp; a common subset of reference assemblies</li>
</ol>
<li>] the new 'asp.net' - is it new, are we starting over, </li>
<ol>
<li>] its a brand new thing that looks a lot like the old thing, it is "concept compatible"</li>
<li>] there still are&nbsp;/controllers, /views,&nbsp;/routes, /actions, /razor,</li>
<li>] BUT IF you go deep down the stack, there is NO system.web</li>
<li>]&nbsp;EXAMPLE -&nbsp;of going from a 'regular car' to a 'hybrid car', the&nbsp;mechanics have changed, but&nbsp;the car&nbsp;still drives the same</li>
<li>] can bring in&nbsp;resources you need, open source taskrunners, javascript libraries,</li>
<li>]&nbsp;its still .net, .net on system.web(as we know it now), .net on windows phone, .net on window, its all .net</li>
<li>] .net represents a lot of different things ( )</li>
<li>] modularity&nbsp;</li>
</ol>
<li>] what are the MAIN benefits of the "new" .net&nbsp;</li>
<ol>
<li>] benefit = the ability to&nbsp;run multiple .net vers&nbsp;side-by-side on 1 server, with different versions of&nbsp;.net on server</li>
<ol>
<li>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</li>
</ol>
<li>] benefits = x/platform -&nbsp;.net apps can now be run&nbsp;ON linux, windows, azure web services and mac platforms</li>
<li>] - app user process&nbsp;</li>
<li>]&nbsp;example - demo in .net deep dive presentation -&nbsp;published a .net app to a&nbsp;usb stick,&nbsp;choosing&nbsp;a random laptop from audience member, .net app works w/out touching anything on the laptop, no registry, no system 32</li>
<li>] &nbsp;.net framework - ships with windows,</li>
<li>] NEW .net core -</li>
<li>] asp.net 5 can target either .net core or .net framework</li>
<li>*] there are implications to your choices, .net core is 11MB, frameworks is 100MB+, it doesnt have all the same stuff</li>
<li>]</li>
</ol>
<li>[07:30] what about Entity Framework 7.x () </li>
<ol>
<li>- concept compatible -</li>
</ol></ol>
&nbsp;
? asp.net or php - web api, mvc, singleR, web pages (EX mads kristensen ) - vs OR vs code
? katana owin and asp.net 5 -
&gt; 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 &gt;
? 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 ,
<h2>[HOW-TO]</h2>
<ol>
<li>] jeffry snowmer</li>
</ol>
<h2>[REFERENCE]</h2>
<ol>
<li>] VIDEO <a href="http://channel9.msdn.com/Events/Build/2015/C9-16" target="_blank">http://channel9.msdn.com/Events/Build/2015/C9-16</a>&nbsp;</li>
</ol>
&nbsp; &lt;iframe src="//channel9.msdn.com/Events/Build/2015/C9-16/player" width="560" height="315" allowFullScreen frameBorder="0"&gt;&lt;/iframe&gt;
&nbsp;
&nbsp;
&nbsp;
&nbsp;
<h1 style="text-align: center;">&nbsp;</h1>