Microsoft Technologies based on the .NET software framework. Miscellaneous topics that do not fit into specific categories.
the upgrade assistance was depreciated and removed from visual studio and replaced with copilot migration. as copilot is not free, there were many complaints, and the upgrade assistance was brought back as a visual studio extension (but with no ongoing support):
https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.upgradeassistant
the success of either method depends on the type of project.
- console app - pretty simple
- winform app - straight forward
- asp.net MVC - depends on coding style. use of HttpContext.Current causes issues. asp.net core is fussier on binding, so you may have runtime issues.
- webform - requires a rewrite. the migration setups a proxy project in asp.net core, so the the site can be migrated a page at a time. copilot may help migrating each webform page to the chosen replacement technology.
suggestions: before migration
- convert all library projects to .netstandard 2.0.
- move from System.Data.SqlClient to Microsoft.Data.SqlClient
- migrate from HttpWebRequest to HttpClient
- remove all references to HttpContext.Current