Upload folder - The global folder where the uploaded files resides. If you do not enter a specific folder for a file upload field in the Edit Tag panel of the Field Setup page, all the uploaded files will be put in this folder.

Important note:

1. Make sure that the Web server user have read/write access to the folder. Please read Configuring Permissions.
   
2. The path is relative to application root. Use slashes "/" as path delimiter, start with "~". e.g. If the application root of your website is C:\Inetpub\wwwroot\demo and you enter "~/uploads/" in this textbox, the folder for the uploaded files will be C:\Inetpub\wwwroot\demo\uploads. If you are not sure which folder is application root, please read Creating Virtual Directories in IIS.

Max File Size - Maximum file upload size in bytes

Allowed file type - The allowed file extensions of the uploaded files. Separate the file extensions (without ".") by comma, e.g. gif,png,png)

Delete file on update/delete - Option to delete the uploaded file when the field value is replaced, removed or if the record is deleted.

Log file folder - The folder where the audit trail log file resides.

Important note:

1. Make sure that the Web server user have read/write access to the folder. Please read Configuring Permissions.
   
2. The path is relative to application root. Use slashes "/" as path delimiter, start with "~". e.g. If the application root of your website is C:\Inetpub\wwwroot\demo and you enter "~/log/" in this textbox, the folder for the log file will be C:\Inetpub\wwwroot\demo\log.

Track login/logout activities - If security feature is enabled, login/logout activities will also be logged.

Server-side - Enable server-side form validation.

Client-side (JavaScript) - Enable client-side form validation.

Note: If the available validation format in the Edit Tag panel (see Field Setup) does not fulfil your requiements, you can use your own server-side and/or client-side validation code using Sever Event and Client Scripts.

Printer friendly/CSV/HTML/Excel/Word/XML - Records can be exported to printer-friendly, CSV, HTML, Excel, Word or XML format. Note that the fields in printer friendly version are same as in List/View page, while the fields in other format are determined by the Export setting of the field in Field Setup page.

XML Encoding - The XML encoding for export data in XML format. (XML document requires encoding so the data can be read by XML parser properly. If your table/field names use English or alphanumerical characters only, you can leave the encoding blank. Otherwise, you need to specify an encoding.)

Enable export in View page - allow export in View pages also

Known Internet Explorer issue:
For known MIME (Multipurpose Internet Mail Extensions) types such as Microsoft Word ("application/ms-word"), the default behavior of some older versions of Internet Explorer is to open the document in the browser. Also, to allow user saving the file with a proper file extension (otherwise the file extension will be .asp), ASP.NET Maker uses content-disposition header to override this behavior by default. For example:
Response.AddHeader("content-disposition","attachment; filename=fname.ext")
When Internet Explorer receives the header, it raises a File Download dialog box. However, if user clicks [Open], Internet Explorer may fail to open the file. Therefore, you may want to instruct user to save the file directly to the user's disk without opening it in the browser.

Notes:

1. Binary data (BLOB fields) cannot be exported.
2. Export to HTML/CSV/XML are not applicable to reports.
3. Images cannot be exported to Word/Excel/CSV/XML.

VB - VB.NET Codes will be generated
C# - C# Codes will be generated

Note: When you change the language, all the language-dependent settings in the project such as server events will become inapplicable, you'll need to convert your code in those settings also. ASP.NET Maker will NOT convert the code automatically.

Target .NET Framework version of the project, available options are 2.0 or 3.5. ASP.NET Maker scripts require .NET Framework 2.0 only, you should only select 3.5 if you plan to add your own code that requires v3.0 or v3.5.

Note: The only differences in the generated scripts are the configurations in the web.config. All other generated code is the same in both versions.

ASP.NET provides two ways that you can organize code within your pages:

code-inline - it is very useful when you want to maintain your code and presentation logic in a single file. By default ASP.NET Maker uses this model.

code-behind - the code for handling events is located in a physically separate file from the page that contains server controls and markup. If Use code-behind file is checked, ASP.NET Maker will use this model.

Various options for setting up the web.config.

ASP.NET Maker generates a configuration file (web.config) for each project. The web.config file contains a nested hierarchy of XML tags and subtags with attributes that specify the configuration settings which control how ASP.NET Web applications behave. Here you can easily specify settings to many commonly used elements such as authentication, sessionState and trace.

For detail description of each field please refer to the Microsoft .NET Framework SDK.

The host name or IP of the SMTP server.

By default the emails will be sent by the default SMTP server on the Web server, in such case you can specify "localhost". But sometimes the default SMTP server may be disabled, in such case you need to specify another SMTP server.

User name for SMTP server authentication. If your SMTP server does not require authentication, leave it blank.

Password for SMTP server authentication. If your SMTP server does not require authentication, leave it blank.

Email address of the sender of all emails

Email address of the recipient(s) for notification emails when a record is added/edited/deleted (if enabled). If there are multiple recipients, separate them by comma.