As in other ABL applications, your OpenEdge session uses the PROPATH to look for the ABL source code for an OpenEdge .NET application. An OpenEdge .NET application includes additional types of configuration and source code files to support the .NET controls. OpenEdge looks for these files in the assemblies directory.

The additional source code files include:

  • OpenEdge internal assemblies — OpenEdge uses several assemblies to provide .NET support for your application.
  • OpenEdge Ultra Controls for .NET — OpenEdge includes support for a set of .NET controls. The Ultra Controls are licensed separately for development environments. However, OpenEdge deployment products install assemblies containing run-time versions of these controls that do not require a separate license. OpenEdge installs these assemblies in the OpenEdge-install-dir/bin directory and looks for them there.
    Note: These installed runtime controls are only supported with .NET Framework.
  • ABL controls derived from .NET controls — OpenEdge handles an ABL class that inherits from a .NET class in the same way as every other ABL class. The application PROPATH must contain the class file or its r-code (.r, .pl, or .apl).
  • Application-specific assemblies — Application-specific assemblies might include third-party controls or your own custom .NET assemblies. You can install these assemblies in the .NET Global Assembly Cache (GAC) (.NET Framework only) or in the application's assemblies directory.
  • .NET Resource Files — Some .NET controls require resource files (.resx) to operate. Resource files are referenced from ABL source files and must be included in the PROPATH.

The additional configuration files include:

  • Assembly References file — The Assembly References file (assemblies.xml) lists the assemblies used by the OpenEdge application. You must deploy this file in the application's assemblies directory. For more information on assemblies.xml, see .NET runtime.
  • Assemblies Application Configuration file (.NET Framework only) — An Assemblies Application Configuration file (assemblies.config) is a means to alter how specific assemblies are loaded in exceptional situations. You must deploy this file in the application's assemblies directory. For more information on assemblies.config, see .NET assemblies.
  • Application Configuration file (.NET Framework only) — OpenEdge might require an Application Configuration file (prow32.exe.config) to configure its internal assemblies. If one is needed, OpenEdge provides the file and installs it in $DLC/bin.
    Note: You should never use or modify this file directly.
  • Runtime Configuration file (.NET Core only) —A runtime configuration file which controls the loading and behavior of the .NET runtime. OpenEdge installs the file in $DLC/bin/Progress.clrbridge.netcore.runtimeconfig.json. The file can be modified but generally there should not be a need to change it.