With all the buzz around Microsoft’s revitalized ASP.NET Core MVC framework, you may wonder what has changed since your “legacy” ASP.NET MVC application was written. Sure, there are new framework features and development tools available; but, which of these things must be adopted and when? Can I still use ASP.NET Web Optimization for bundling & minification, or do I have to use something like Gulp? Which package manager(s) should I use to acquire the requisite bits and assets? How does the framework support dependency injection for my controllers? Should I target .NET Framework, .NET Core, or both? What are the repercussions of my IDE or editor selection? Lend me 60 minutes of your time, and I’ll answer these and some other frequently asked questions. You’ll leave with a clearer picture of a practical migration path for your aging MVC application.