ProgramCore
The role of the core execution plug-in loader of the platform to dynamically load the plug-in. The plug-in this system is a component defined by the manifest XML file. The core understands the installed plug-ins and their functions. Function is added to the core using the usual directory method (). The path points to a fully defined extension point. The plug-in can be used to provide some functions or expand the platform. By adding paths to the extension tree, the plug-ins can be expanded by other plug-ins in sequence.
The extension tree is the only mechanism that adds functionality to the platform and Other plug-ins. All plug-ins use this method.
Because the. NET platform is used, extensions can not only use the C # language, but also plug-ins can be created in other. NET languages, including third-party languages that implement. Net specifications.
Global attributes
The property engine stores all types of configuration variables. There is an application-wide property class that stores custom properties in a file in the current user's personal folder.
Resources
Current applications need the ability to locate resources. The core defines a class for locating files and images for applications.
Gui Layer
To some extent, it is always a good idea to extract specific GUI APIs due to application requirements. Therefore, the core defines a very thin layer to encapsulate windows. Form APIs. This method allows applications to easily switch to other GUI development kits (that is, without changing other programs, you only need to apply different GUI packages to make the interface have different styles ).