Settings and Constraints Editor
Application Designer provides access to a complete model of application configuration settings and the ability to define hosting constraints using the Settings and Constraint Editor. Hosting constraints allow system architects to specify requirements on the hosting environment. By defining hosting constraints on application definitions in the Settings and Constraints Editor, application developers can request a required set of features be available in the target deployment environment, thus communicating to infrastructure architects important application requirements. The infrastructure architect can then decide whether they want to make changes to the logical datacenter to accommodate those requests. The application settings and hosting constraints are validated against logical datacenter settings and constraints as part of deployment validation.
Once the datacenter is described, the infrastructure architect can also specify policy constraints regarding the types and configuration of applications that can be hosted in the representation of the datacenter using the Settings and Constraints Editor. These constraints are authored against settings in the application layer because they are used to constrain the types of applications the servers can host and to specify the configuration required for the applications. For example, ASP.NET security settings can be constrained for applications hosted on a Web server or the version of the .NET Framework required for applications hosted on a Windows Client logical server. Marking certain settings as not overridable (that is, fixed) specifies that these settings cannot be overridden during system design.