Enterprise-level agile software development platform agileeas. Net-plug-in running container Based on DOTNET Component Technology

In the previous plug-in interface imodule of agileeas. net, we introduced the plug-in contract of the EAS. Net module. In this article, we will introduce the running container that calls the plug-in, that is, the platform.

Agileeas. NET platform was first used to develop and manage information system applications based on winform technology. Therefore, winform-based running containers are the most mature. We provide three types of running containers using winform technology: traditional winform containers, smart client-based running containers, and activexform containers based on the combination of winform and webform technologies also provide running containers based on pure webform technology.

I will post the running effects of traditional winform containers and smartclient containers as follows:

If you can't see the image clearly, open the source image. This is the running effect of the winfrom technology-based plug-ins. Currently, there are two ways to run the plug-ins in containers, the first type is directly embedded into the container interface, such as a tabCodeOne module plug-in and the other runs in an independent winform mode, such:

We provide two module plug-in navigation methods based on the navigation list, tool bar, and menu. By default, the left navigation list or navigation tree is automatically collapsed. In a specific application project, you can select the navigation method as needed. One leaf item in the menu or navigation points to a target module plug-in.

After an operator (account) logs on to the platform, the platform permission check system loads the module with the execution permission of the logon operator and loads it to the business navigation bar and navigation menu. Finally, the logon interface is shown.

 

Note: agileeas. to support the release and change of application developers, a resource system is developed for the container running interface, the application developer can change the resource file in the configuration file to change the system name and display images. For example:

Based on the standard winform container, the smartclient runtime container adds the Smart Client support, including the intelligent deployment and upgrade of the application system and the optional Distributed Data Access. Below is a brief demonstration of the webfrom runtime container.

In these running containers, the Platform calls plug-ins. But in some applications, the module plug-ins need to call other module plug-ins. How can we do this? We have extracted a basic interface, iapplication:

 Iapplication  /// <Summary>  /// Define the basic specifications of the platform application (container.  /// </Summary>  Public   Interface Iapplication { /// <Summary>     /// Obtain the applicationProgramName.      /// </Summary>      String Name { Get ;} /// <Summary>      /// Run the module.      /// </Summary>      /// <Param name = "module"> module type. </Param>      Void Runmodule (type module ); /// <Summary>      /// Run the module.      /// </Summary>     /// <Param name = "module"> module guid. </Param>      Void Runmodule (guid module ); /// <Summary>      /// Run the module.      /// </Summary>      /// <Param name = "module"> module instance. </Param>      Void Runmodule (imodule module );}

In the iapplication interface, we define the runmodule method. The plug-in can call other imodules through the iapplication in the upper and lower layers of the agileeas. NET application.

 

I will Article , I will introduce the extended system of activexfrom running containers and plug-ins.

 

link: Introduction to agileeas. NET application development platform