ASP.NET Settings General Options
| CodePage |
Codepage to be used for your web site |
| LCID |
Locale ID to be used for your web site |
| Default Date Format |
yyyy/mm/dd, mm/dd/yyyy, dd/mm/yyyy,
yyyy-mm-dd, mm-dd-yyyy, dd-mm-yyyy,
yyyy.mm.dd, mm.dd.yyyy, dd.mm.yyyy |
| Session Timeout |
The length of time in minutes before an idle session is terminated. If blank or 0, default setting (20 minutes) of the server will be used. |
| No Cache |
Whether caching is required on browser |
| Records per page |
Number of records to be displayed on the list page of all tables.
If blank or 0, default setting of 20 will be used. |
| Selectable page sizes |
Number of records to be selected by user. Comma separated values,
e.g. 10,20,50,ALL.
Note: "ALL" (without
quotes) is supported, other values must be integers. |
| Paging section style |
"NumericPages" or "NextPrev" |
| Sort type |
None, Single column or Multiple
column. If Multiple column is selected,
the generated list page supports multi-column sorting by Ctrl-clicking
the table header. |
| Paging section at top |
Show the paging section at top |
| Paging section at bottom |
Show the paging section at bottom |
| Export |
Records can export to HTML, Excel or Word format.
HTML format can be used as a printer friendly version.
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 your output file extension, e.g. .asp), ASP.NET Report 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. |
.NET-Specific Options
| Language |
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.
|
| Version |
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.
|
| Use code-behind file |
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. |
| Web.config |
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. |
|
