Enterprise-level agile software development platform based on DOTNET component technology-agileeas. Net-plug-in interface imodule Extension

PreviousArticleAgileeas.. Net plug-in interface imodule and agileeas. net plug-in runtime containers provide an introduction to the basic contract meanings of plug-ins and runtime containers. However, during development, this interface is not implemented for each module, we provide some basic implementations for some curved applications. application developers can choose to continue with this basic implementation to implement specific functions.

In the winform application, the implementation of moduleform and modulecontrol imodules is provided by default. Developers only need to rewrite the guid, modulename, description attribute and run method during application development.

In the webform application, moduleform and modulecontrol are also provided. For more information, see the class library help.

The following is an example:

 Paycalc2      Public Partial Class Paycalc2: EAs. Windows. UI. Forms. moduleform { Public Paycalc2 () {initializecomponent ();}Public   Override   String Modulename { Get { Return " Loan calculation Machine ";}} Public   Override Guid { Get { Return   New GUID (" CD151DE6-0475-4d68-9DFE-AD272112B318 ");}} Public   Override   String Description { Get { Return " Gadgets used to analyze mortgages ";}} Public   Override   Void Run ( Params   Object [] Parameters ){ This . Mdiparent =Null ; This . Showdialog (EAS. Windows. application. instance. Shell );} // Other ServicesCode }

In addition, some basic implementations related to ORM Data Objects and interfaces are also provided. I will describe this part in detail later.

The following article describes how to implement a module plug-in based on Attribute tags.

 

Link: agileeas. NET application development platform Introduction

Agile parallel development method of agileeas. net

Agile Software Engineering Lab