Migrate the primary website—including the OnTopic components—to ASP.NET Core 3.0.
Basic Approach
While much of ASP.NET Core remains compatible with ASP.NET MVC Framework 5.x, there are some differences, especially in terms of how the application is declared, bootstrapped, and configured. There are also some (minor) differences in the Razor syntax.
Open Questions
[x] Find URL Rewrite approach
[x] Find configuration for Application Insights
Core Elements
[x] Migrate csproj file to Visual Studio 2017 format
[x] Establish Program.cs class for bootstrapping app
[x] Migrate from DefaultControllerFactory to IControllerActivator
[x] Remove dependency on legacy TopicRepository ambient context
View Elements
[x] Move static files to wwwroot
[x] Change @Html.Partial to <partial /> tag helper
[x] Migrate format for @helpers to HTML @functions
Most of these changes have all been demonstrated on the Topics-AspNetCore-Sample site—though that is still based on ASP.NET Core 2.0 and still needs to be upgraded to take advantage of e.g. new support for Razor outputting functions.
Migrate the primary website—including the OnTopic components—to ASP.NET Core 3.0.
Basic Approach
While much of ASP.NET Core remains compatible with ASP.NET MVC Framework 5.x, there are some differences, especially in terms of how the application is declared, bootstrapped, and configured. There are also some (minor) differences in the Razor syntax.
Open Questions
Core Elements
csprojfile to Visual Studio 2017 formatProgram.csclass for bootstrapping appStartup.csto ASP.NET Core formatDefaultControllerFactorytoIControllerActivatorTopicRepositoryambient contextView Elements
wwwroot@Html.Partialto<partial />tag helper@helpers to HTML@functionsMost of these changes have all been demonstrated on the Topics-AspNetCore-Sample site—though that is still based on ASP.NET Core 2.0 and still needs to be upgraded to take advantage of e.g. new support for Razor outputting functions.