Previous Topic: General (GUI and .NET)Next Topic: Global Assembly Cache (.NET only)


ASP.NET (.NET only)

When you select ASP.NET from the MSI .NET Assemble Details panel, the following dialog appears:

MSI .NET Assemble Details panel with ASP .NET selected

The fields in the ASP.NET dialog are described in the following list:

Compress Dynamic Content

Allows you to compress the dynamic HTML content returned to the browser.

Pre-compile ASPX pages

Allows you to compile an ASP.NET application before deployment.

Browser Controlled History

Allows the Back and Forward buttons of your browser to be used for navigation. The default style allows access to only one page at a time. Although the Back and Forward buttons remain enabled, using them takes you out of the application.

Threaded

Allows the runtime to create an extra thread in addition to the one the Application Server creates for each request. This option is essential for applications that use MessageBox and MessageBoxBeep. In Web Generation Applications, message boxes and OCX controls require threading to be enabled.

Auto-Include Third Party Control Assemblies

If selected, includes any third-party web control assemblies that you used in your application and any assemblies they reference, in the MSI file. You can also use the Additional Files dialog if you want to specify them yourself.

Important! This feature is provided for your convenience, however, CA has no way of knowing whether these third-party web controls are properly licensed on your deployment environment. Therefore, it is your responsibility to ensure proper licensing on the target machine.

Exclude Assemblies in GAC

Enabled only when Auto-Include 3rd Party Control Assemblies is selected. When selected and enabled, any third-party web control assemblies that are deployed in GAC are not included in the MSI file. By default, this field is disabled and not selected.

Session State

The Web is a stateless environment. However, most web applications require effective state management. In particular, the session state of a web application is the data that an application caches and retrieves across different requests. A session represents all the requests that are sent by a user during a connection to the site. The session state is the collection of persistent data that the user generated and used during the session. The state of each session is independent from that of another session and does not survive the end of the user session.

The modes that are supported are:

StateServer

Session values are serialized and stored in the memory of a separate process (aspnet_state.exe). The process can also run on another machine.

SQLServer

Session values are serialized and stored in a Microsoft SQL Server table. The instance of SQL Server can run either locally or remotely.

InProc

Session values are stored in the memory of the ASP.NET worker process. Thus, this mode offers the fastest access to these values. However, when the ASP.NET worker process recycles, the state data is lost.

For more information, see the Microsoft documentation about ASP.NET state management.

Session State Timeout

Specifies the number of minutes a session can be idle before it is abandoned. The default is 20. The Timeout range is from 1 through 1440 minutes.

Connection String

Required for both StateServer and SQLServer Session State modes. The IP address can be in IPv4 format or IPv6 format.

For StateServer

Known as stateConnectionString. It specifies the server name or IP Address and port number where session state is stored remotely. For example, tcpip=127.0.0.1:42424.

For SQLServer

Known as sqlConnectionString. It specifies the connection string for a SQL Server. For example, data source=localhost;Integrated Security=SSPI;Initial Catalog=northwind.

Encrypt sessionState section (web.config)

Encrypts the sessionState information. It is selected by default.

Custom Errors

Specifies whether custom errors are enabled, disabled, or shown only to remote clients.

On

Specifies that Custom Errors is enabled. If no defaultRedirect is specified, users see a generic error.

Off

Specifies that Custom Errors is disabled. This allows display of detailed errors.

RemoteOnly

Specifies that Custom Errors are shown only to remote clients and ASP.NET errors are shown to the local host. This is the default.

Default Redirect

Enabled only when Custom Errors is On. It specifies the default URL to direct a browser to if an error occurs. The URL may be absolute (for instance, http://www.myapp.com/ErrorPage.htm) or it may be relative. A relative URL such as ErrorPage.htm is relative to the Web.config file that specified the defaultRedirect URL, not to the Web page in which the error occurred. A URL starting with a slash (/), such as /ErrorPage.htm, means that the specified URL is absolute to the root path of the Application Server.

Display Mode
Dialogs

Enables modal and modeless dialogs in a web application.

Classic

All windows are embedded in the same browser.

Idle Threads

Specifies the minimum number of idle threads that are created and maintained by the ThreadPool. They are managed in a background task and used to serve incoming requests to reduce the time that is spent in creating and destroying threads when new requests are initiated or existing ones complete. Tuning this value can help optimize your application performance. For more information, see the Microsoft documentation.

Theme Name

Specifies the directory where the skin and the images are stored.