The Grumpy Old Programmer s First MV6.NET Core App

Transcription

1 The Grumpy Old Programmer s First MV6.NET Core App Paul Litwin Fred Hutchinson Cancer Research Center

2 Slides & samples can be found here Litwin Grumpy Old MVC 6 2

3 Litwin Grumpy Old MVC 6 3

4 Session Itinerary Web Dev Options in Visual Studio 2015 ASP.NET 5 & MVC 6 Entity Framework 7 Building a ASP.NET 5 web site Targeting the Full vs Core CLR Grumble, grumble Litwin Grumpy Old MVC 6 4

5 Web Development in VS 2015 A tale of two ASP.NET s ASP.NET 4.6 is still there & will be supported And then there s ASP.NET 5 Litwin Grumpy Old MVC 6 5

6 VS 2015 and ASP.NET 4.6 This is the same ASP.NET you know Minor changes from ASP.NET Same project structure Existing ASP.NET 4.x apps from VS 2013 should migrate with zero changes A reasonable option to continue to use Litwin Grumpy Old MVC 6 6

7 ASP.NET 5 ASP.NET reinvented! Out with the old No Web Forms No VB but it will be added at a later date Bloat factored out (when targeting CoreCLR) In with the New! Project structure significantly different Lots of details have changed Cross-platform development and hosting Windows, Linux, OS/X MVC and WebAPI now combined together Litwin Grumpy Old MVC 6 7

8 ASP.NET 5 Development ASP.NET 5 is now MVC + Web API + client-side development Revamped file structure Takes advantage of Rosyln compiler Strict separation of static assets from programming logic Ditches web.config for.json files Uses npm (server-side), bower (client-side), and nuget (.net server-side) for managing packages Uses gulp for client-side building Built-in support for dependency injection Litwin Grumpy Old MVC 6 8

9 MVC 6 Hard to separate out MVC specific-changes from ASP.NET, but here s a couple Tag helpers Alternative to Html => model.description, new = "bigblue" }) becomes <input asp-for= "Description" class = "bigblue" /> See for good Tag helper reference Unified MVC and API controllers Methods now return IActionResult instead of ActionResult Litwin Grumpy Old MVC 6 9

10 ASP.NET 5 Runs on CoreCLR & Full.NET Frameworks CoreCLR is a subset of the.net Framework Much smaller footprint Optimized for cloud Optimized for cross-platform Contains only minimal, core functionality Optional features are added as nuget package Pay for play.net 4.6 Framework Old, familiar framework with all the goods Much larger footprint than CoreCLR Litwin Grumpy Old MVC 6 10

11 Entity Framework 7 Story parallels the pairing down of ASP.NET 5 Rebuilt from ground up Object context has been tossed Much of DbContext is there, but not everything Lazy loading not there Find method not there Later betas will add more features Litwin Grumpy Old MVC 6 11

12 The Microsoft Stack Litwin Grumpy Old MVC 6 12

13 Demo Time to Build a Modern Web Site Litwin Grumpy Old MVC 6 13

14 What Happened to My Project? Litwin Grumpy Old MVC 6 14

15 So what s different? Web.config replaces with project.json and a few other json files Global.asax.cs & App_Start replaced by Startup.cs Static files moved to wwwroot folder No cool scaffolding of controllers & views This should change in later releases Litwin Grumpy Old MVC 6 15

16 Demo So what does it take to migrate an existing ASP.NET 4.5/MVC 5/EF 6 App to ASP.NET 5/MVC 6/EF 7? Detailed steps can be found in my recent blog post: Litwin Grumpy Old MVC 6 16

17 Migration Issues Encountered You register EF 7 DbContext as a service in startup.cs; inject DbContext into your repository classes Various library names have changed; System.Web is gone EF 7 (currently, at least) has no find method and doesn t support lazy loading Routes are handled in startup.cs Various miscellaneous changes You aren t required to use Tag helpers; you can still use Html helpers Litwin Grumpy Old MVC 6 17

18 Which Platform? If possible, you should target the Core CLR Cloud optimized Scales better Cross-platform Targeting the.net 4.5 CRL should be your fallback plan Litwin Grumpy Old MVC 6 18

19 Choices, choices Hi, I m ASP.NET 4.5 with MVC 5 and Entity Framework 6 Hi, I m ASP.NET 5 with MVC 6 and Entity Framework 7 Litwin Grumpy Old MVC 6 19

20 Comparing the old to the new ASP.NET 4.5 MVC 5 EF 6 ASP.NET 5 MVC 6 EF 7 Familiar Predictable Stable Heavy footprint; not optimized for cloud Only runs on IIS on Windows Can run on.net 4.x CLR Can work with dependency injection Support for client-side development Use Html Helpers Choose Web Forms, Web Pages, MVC Choose C# or VB EF 6 supports lazy loading New Requires significant relearning Unstable; changing (beta) Optimized for cloud when deployed to Core CLR Can run on Windows, Linux, and Mac Can run on.net 4.6 or.net 5 Core CLR Dependency injection is baked in Embraces client-side development Uses Tag Helpers Choose MVC Choose C# (VB promised) EF 7 doesn t support lazy loading yet Litwin Grumpy Old MVC 6 20

21 Grumble, Grumble Should I embrace the new ASP.NET 5 or Litwin Grumpy Old MVC 6 21

22 Closing Grumble Though it require some re-learning, I like the new ASP.NET 5, believe the advantages outweigh the disadvantages, and develop with it when it is released Of course, it s still in beta, so we will see how the later releases shape up I m happy to let go of Web Forms, VB, and the bloat of the old ASP.NET In summary: yes, it s worth it! Litwin Grumpy Old MVC 6 22

23 Thank you! Slides & samples can be found here Litwin Grumpy Old MVC 6 23