How to: Specify Dynamic or Static Content for ASP.NET Applications
In Application Designer, you must specify whether an ASP.NET application exposes dynamic or static content. Dynamic content specifies that a script processor such as ASP.NET is required to run the application or any Web services associated with the application. Static content specifies that no script processor is required, for example, to run the application or to display HTML.
Note
The Web server that will host the ASP.NET application is represented as an IIS Web server on the logical datacenter diagram that you use to define and evaluate deployment for the system. The IIS Web server uses the WebSvcExtRestrictionList setting to indicate whether a script processor is installed, among other functions. The WebSvcExtRestrictionList setting is an implicit setting, which cannot be edited. However, you can view this setting using the Settings and Constraints Editor. To view the WebSvcExtRestrictionList setting, open the logical datacenter diagram and select the IIS Web server to which the ASP.NET application will deploy. In the left pane of the Settings and Constraints Editor, navigate to Logical Server Settings, InternetInformationServices, and then WebSites. In the right pane, navigate to Capabilities, and then WebSvcExtRestrictionList. Under this setting, locate the version that specifies that ASP.NET is installed. You can also use the search functionality in the Settings and Constraints editor to locate this setting. For more information, see Implicit Constraints and Applying Settings.
To specify dynamic or static content for an ASP.NET application
Select the ASP.NET application definition you want on the application diagram.
In the Properties window, set the Web Content property to Dynamic (default) or Static.
Tip
If the Properties window is not visible, choose Properties Window from the View menu or press F4.
When you select dynamic content for an ASP.NET application and then use Deployment Designer to define and evaluate deployment for a system containing that application, Deployment Designer validates a constraint. This constraint determines whether the Web server that will host the ASP.NET application has a script processor installed. For more information, see Overview of Deployment Designer.