A template is a zip file of code snippets needed to generate the output files. Template is fully customizable, you can customize the default template shipped with the product to suit your own needs in your web applications.
Zipped Template, Unzipped Template and Template Cache
To generate output files, the code generator first unzips the template to the subfolder \<product name>\Templates\<template name> under your Documents folder, pre-processes the scripts in the template into template cache, then use the template cache to generate output files. If the unzipped template already exists, the code generator will skip the unzip process and reuse the template cache so the time required for generation is minimized.
If you want to customize a template, normally you customize the files in the zipped template, but you'll need to zip it back after customization, for example, by dragging the customized files back to the zipped template. The unzipped template under the Documents folder provides an optional way to customize the template without re-zipping the template. Either way, you should zip it back after all the customizations are done.
If you prefer to work with the unzipped template but you have not generated any files yet, do once first. Then you can modify the unzipped files under the subfolder named "Script". For example, if the template archive is named as "default.zip", it will be unzipped to the folder <document folder>\<product name>\Templates\default\, you can modify files under the subfolder "Script" under it.
When changes in the zipped template is detected, the code generator will ask you to confirm overwriting the old unzipped version, you should answer carefully, especially if you've implemented some customizations previously. Always back up your customized template first!
The core of the template file is a control file named control.xml. It is an XML file containing all the necessary instructions for the generation process. During generation the code generator will parse the control.xml and follows the instructions to generate the output files one by one. If you want to add an output file, you need to add a <control> tag in the control file. If the file is to be included in other file(s), you may need to add <session> tags in control.xml also. See Control File for details.
All the phrases in the template are separated into a single XML language file for easy translation to other languages and sharing. If you want to translate a template, this should be the only file you need to translate.
Language files are placed in the subfolder "languages" under the installed folder. The files are used for all templates.
See Multi-Language Project for more information on making a language file.
Locale files containing locale settings for number, currency, date and time formatting. Each locale file has a language ID, which must match the corresponding language file.
Locale files are placed in the subfolder "locales" under the installed folder and they are used by all templates.
Many locale files are already provided in the "locales" folder, you can edit them or even add your own locale files. To edit a locale file, just open the locale file with any text editor supporting utf-8 file and then edit your locale settings. To add a locale file, just copy any existing locale file, and then edit it.
A locale file is in JSON format, when you edit it, make sure you do not break the JSON format. Always save the file in utf-8 format without BOM.
Currently the "time_zone" setting in the locale files is not supported.
The template files and output files are in ASCII encoding by default. Since the phrases are separated into XML language files in utf-8 encoding, ASCII encoding will suit most cases as the scripts contain code only. When you customize a template, it is recommended you use the language file also. If you have to put unicode characters directly in the template files, you must always use utf-8 and save the file in utf-8 encoding with the byte order mark (EF BB BF).
To change the general layout, just modify the file "template.cshtml" in the template. This file will be generated as a layout page for the ASP.NET application.
Template Tags and Object Properties
The code generator processes the Template Tags, assembles the output files using the code snippets from template files and generate code according to Template Object Properties. Template object properties are project settings either inputted from the user interface or restored from a project file. Template Tags are in the format of HTML comment, when you customize template you should use an editor that will not unexpectedly alter or remove the HTML comments, otherwise incorrect result may occur.
User Code File
Advanced users can customize the dynamically generated code by overriding an existing template tag using User Code. To override an existing template tag, you need to add your own function in the User Code File. (See Using User Code.) By default, the User Code File is named as "usercode.js" and can be found under the "src" subfolder of the installed directory.
You can use your own custom functions in the template. To use custom functions, write and put them in the User Code File. Then just use template tag to call them in the template. (See Using User Code)
Integrating third-party tools can be done by extensions. An extension is modification of template to make the template supports additional feature(s) implemented in the extension. An extension has the same structure as template and you can modify them in exactly the same way as modifying the main template. Extensions are processed after the main template, it may add or change some files in the template. Extension supports User Code also.
Extensions files (in zipped format) must be placed under the subfolder "extensions" of the installation folder. Each extension must have a XML description file so the product can load the available extensions in the user interface for selection. You can open an XML file in the "extensions" subfolder to see the content, which is self-explanatory.
Read Tools on how to select extensions for a project before generation.
Also see Third-party Tools for more information on the third-party tools.
Note All extensions are only provided as examples on how to extend the template with your own code or your own implementation of third party tools, all third party tools used in them are not developed by the author of ASP.NET Maker and are not part of ASP.NET Maker, NO TECHNICAL SUPPORT WILL BE PROVIDED.
Custom View Tag is same as extensions except that it is used to display a field in the List and View pages with your own code. A Custom View Tag has the same structure as extension and you can modify them in exactly the same way.
Custom View Tag files (in zipped format and XML format) must be placed under the subfolder "customviewtags" of the installation folder. Each Custom View Tag must have a XML description file so the product can load it in the Field Setup page for selection.. You can open an XML file in the "customviewtags" subfolder to see the content, which is self-explanatory. Unzip the extension and see how it is implemented.
Read Field Setup on how to select Custom View Tag for a field.
Custom Edit Tag is same as extensions except that it is used to display the Edit Tags of a field (e.g. in Add/Edit pages) with your own code. A Custom Edit Tag has the same structure as extension and you can modify them in exactly the same way.
Custom Edit Tag files (in zipped format and XML format) must be placed under the subfolder "customedittags" of the installation folder. Each Custom Edit Tag must have a XML description file so the product can load it in the Field Setup page for selection. You can open an XML file in the "customedittags" subfolder to see the content, which is self-explanatory. Unzip the extension and see how it is implemented.
Read Field Setup on how to select Custom Edit Tag for a field.