If you wish to migrate an ABL application that uses .NET Framework from Windows to Linux, consider migrating it from .NET Framework to .NET on Windows first, if possible (see Migrate from .NET Framework to .NET on Windows). While not strictly necessary, this may provide an easier transition by maintaining the operating system while migrating from one .NET runtime to another.

You cannot migrate an OpenEdge .NET Desktop application that has graphical user interface code. However, you can migrate ABL code that accesses .NET classes from the character client (CHUI), the ABL batch client, or the Progress Application Server (PAS) for OpenEdge agent.

For those applications that can be migrated, moving from .NET Framework to .NET will most likely require assembly changes. Ensure that any .NET Framework-specific assemblies are replaced with .NET-compatible libraries. This may be easier to do on Windows since the development tools (such as Microsoft Visual C++) are only available there.

Once the application is working under .NET on Windows, you can then attempt migration to Linux. Many .NET libraries that do not involve any GUI components will work without modification on both Linux and Windows. However, if the ABL application requires changes, it may be easier to do this step-wise, instead of trying to migrate both platform and .NET runtime concurrently.