Starting v4.0 the Quick Objects Designer now allows you to configure multiple templates to produce any kind of code, text, html, or xml etc.
The following screen shot shows the "Template Configuration" area on the "File Paths" tab under the Project Properties.
Click to enlarge
The included templates are by default placed in the {Install Directory}\NET20\BIN\Templates folder. The provided templates can be used to generate various types of code and these can also be used as samples to build custom templates. If you need further information or help in creating custom templates for your needs please contact us. The following templates are included:
Templates that produce C#
- Table_NameBase.cs.template (Produces base business logic classes)
- Table_Name.cs.template (Produces business logic classes that inherit from the base classes)
- View_NameBase.cs.template (Produces base classes for the typed views)
- View_Name.cs.template (Produces classes for the typed views that inherit from the base classes)
- Procedure_List.cs.template (Produces one class that contains methods for each of the enabled stored procedures)
Templates that produce VB.NET
- Table_NameBase.vb.template (Produces base business logic classes)
- Table_Name.vb.template (Produces business logic classes that inherit from the base classes)
- View_NameBase.vb.template (Produces base classes for the typed views)
- View_Name.vb.template (Produces classes for the typed views that inherit from the base classes)
- Procedure_List.vb.template (Produces one class that contains methods for each of the enabled stored procedures)
Templates that produce XML (To be used with the WebXmlForm component)
- XmlForm_Edit_Table.xml.template (Produces one file that contains xml form definition that can be used by to provide insert/update capabilities for a single record in a table.)
- XmlForm_List_Table.xml.template (Produces one file that contains xml form definition that can be used by an instance of WebXmlForm component to create a grid showing data from the table.)
The templates can executed in two ways. One method is to execute the template for each Table, View or Stored Procedure and results in creating one file each corresponding to the Table, View or Stored Procedure. The other method is to execute the template once and hence the template will handle All Tables, Views or Stored Procedures. Various execution modes available are explained below:
- ForEachTable (Only use with Table_Name*.template as these templates will create one class/file for each Table that is enabled.)
- ForEachView (Only use with View_Name*.template as these templates will create one class/file for each View that is enabled.)
- ForEachProcedure (None of the provided templates use this mode. However this can be used with any custom templates that need to produce one file per active procedure.)
- AllTables (None of the provided templates use this mode. However this can be used with any custom template that need to produce one file for all active tables.)
- AllViews (None of the provided templates use this mode. However this can be used with any custom template that need to produce one file for all active views.)
- AllProcedures (Only use with Procedure*.template as these templates will create one file that will contain all active procedures as methods)
Lets consider the example settings below demonstrating how to setup a template for a certain type of execution and output.
Once the templates are configured, the Generate menu is populated with the templates that are enabled as shown in the screen shot below.
