How to: Apply a Setting
Settings are configuration elements in the application environment or the application hosting environment that control either the behavior of the application or the runtime environment. You edit settings on applications, logical servers, endpoints, and zones using the Settings and Constraints Editor. For more information, see Settings and Properties.
Use the following procedure to apply a setting.
To apply a setting
Select the item to which you want to apply a setting.
Settings can be applied to application definitions, applications, systems, endpoints, logical servers, and zones.
Expand the Settings node in the Settings and Constraints Editor.
Select the setting you want to apply. For configuration settings, you will need to add the specific setting resource before you can modify the setting. For more information, see How to: Add Resources.
Enter the setting value in the Value field.
Press ENTER or click outside of the Value field to commit the setting.
Set the Overridable, Deployment, Null, and Use Default attributes, as needed.
Tip
To change a modified setting in Application Designer or Logical Datacenter Designer back to its original default value, select Use Default. In System Designer, selecting Use Default changes an overridden setting to the current value on the underlying application or endpoint definition.
For more information, see Settings Attributes.
You can also add your own custom settings to any item for which you can apply a regular setting. For more information, see How to: Create Custom Settings for Applications, Servers, Endpoints, and Zones.
Security
Visual Studio saves predefined settings and custom settings as plain text (unencrypted) in System Definition Model (SDM) documents such as distributed system diagram (.ad, .ldd, and .sd) files, application definition (.sdm) files, and custom prototype (.adprototype and .lddprototype) files. For more information, see Overview of the System Definition Model (SDM) and Extending Distributed System Designers. For certain settings, Visual Studio display masked versions in parts of Distributed System Designers and does not save them in .sdm or .ad files. For more information, see Considerations for Implementing Applications. Therefore, avoid storing sensitive, confidential, or proprietary data in settings where masked versions are not displayed and be aware of this consideration prior to distributing these files.
See Also
Tasks
How to: Specify Application Settings as Overridable