To develop and implement MX-Frame project certain steps in development procedure are required and instructions to follow. Creating MX applications using these instructions and steps is the fastest way to build and develop user friendly and reliable software.

Each of this steps is equally important and requires at most attention in order for the application to be developed on the highest level.

1. Before the developer can start using MX-Developer it is necessary to have data layer defined in a desired data source. If SQL data source is used at least tables must be defined. From these tables data will be displayed in the application. It is highly recommended that views, stored procedures and functions are also implemented and that this objects are used to provide data from database. If only SQL tables exist it is also possible to write SQL statements in MX-Developer to provide the desired data. 
2. After data layer and the content of the application is defined MxLibrary project must be created. For instructions on how to create MxLibrary project see chapter Creating MxSolution. 
3. Next step is to create MxAdapter component. Adapter provides the desired data from a data source. In adapter developer specifies the type of data source, the data to display, sets data appearance and data behavior, defines readable and writable statements and their parameters, sets execution conditions, runtime connection strings, foreign keys etc. How to create and define an adapter and its components is better described in chapter Designing a Data Access Layer. 
4. After data access layer is defined user interface be designed. It is designed with MxPart component. A part is basically a user interface on which data from adapter will be presented to the user. Data can be presented to the user with the help of various MX components. Everything on how to create and design a part is described in chapter Designing a User Interface. 
5. In order to display parts or user interfaces navigation must be implemented in the application. Navigation is implemented with MxNavigationMenu component. Navigation in MX-Client is implemented with a ribbon. Therefore in order for a part to be accessible to the end user a menu must be created. Appearance and behaviour of the menus can be set by defining their properties. Menus, their creation and the use are better described in chapter Designing a Navigation. 
6. Last MX-Developer component to implement before an application is ready to use is MxBootstrapper. Using this component MxLibrary projects can be recognized in MX-Client. How to define this component is described in chapter Designing a Bootstrapper.  
7. After the last development step is finished the project just needs to be re-builded and the solution is ready to be used in MX-Client. Every new MxLibrary must be registered before its content is visible in MX-Client. This is done automatically when building the project. See post build events of the project for more details.

After all steps above are completed user can start using the application. Of course strategy described here is only one variations of development procedure. Strategy can be changed and adjusted to the needs and desires of developer or development team, but in principal the order of steps remains the same.

See Also