Skip to content

General considerations

Jump to bottom
Michael Ketting edited this page Feb 1, 2023 · 1 revision

Follow standard migration procedures

See Overview of porting from .NET Framework to .NET

Plan and evaluate first

When porting a large application to .NET Core, several issues might arise. Identify the risks and try to find solutions before you port the bulk of the application.

Typical problem areas include:

  • Libraries:
    • .NET Framework libraries and classes that are not supported in .NET Core, or are provided in versions that differ from their old .NET Framework version (often identified by a "Core" prefix or suffix, as in "Core WCF").
    • Third-party libraries, including Open Source and commercial: consider replacing with updated versions or alternative libraries. For Web Forms control libraries, consider using the CoreForms .NET Framework Bridge
  • Infrastructure dependencies:
    • Authentication
    • Dependencies on low-level configuration (e.g. IIS-specific settings)
    • Low-level code (e.g. caching, error handling)

We recommend the following steps:

  1. Use the PortabilityAnalyzer to identify potential problems
  2. Create a small test application to try out solutions to hard migration problems
  3. Estimate effort and identify remaining risks

Isolate migration concerns

Before you port a complex application to .NET Core, you shoud gather some experience with .NET Core and generic upgrade mechanisms.

Learn how to upgrade a .NET Framework project to .NET Core before you attack more complex problems like WCF or Web Forms.

Note that CoreForms is not yet supported by a large community. You are much more likely to find solutions to errors and problems or for generic migraition issues, but also for specific scenarios like a Core WCF migration or OSS library usage. Make sure you get this kind of issues out of your way first.

Clone this wiki locally