If you mean only the database configuration (connection strings), you can still use the old approach, because Sitefinity data configuration is implemented to work with both DataConfig.config
. However, bare in mind that, if you have connection strings with the same name, that one in the DataConfig.config
will override the other one in the web.config
Can you specify what kind of configuration you want to differentiate between environments?
Regarding Sitefinity 4.0 configuration, you could have different configuration in different context. This could be accomplished by Configuration Policy. Currently, we have 2 policy handlers: UserPolicyHandler
. For example, you can persist different configuration settings a specific user( or role), then if the current user is this user (or belongs to this role), this settings are applied.
It is not implemented yet, but, in the same way, you could implement a custom PolicyHandler, e.g EnvironmentPolicyHandler or DomainPolicyHandler, and persist different configuration for different environments. We hope to include this functionality in the Q2 as a part of the Personalization module, which will be based on configuration policies.
We hope this will handle any scenario. Please, do let us know if you have any notes?
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Public Issue Tracking
system and vote to affect the priority of the items