Topics

All topics

Rules for creating custom configuration files

If you need to create a custom configuration file that will be stored on the file system, make sure:

The configuration is related to the system setup and does not need to be changed runtime
It contains configurations that need to have different values on the different environments. For example, SMTP settings need to be different on the Test and the Live environments, in order not to spam your customer’s accounts with test data.
The configuration is not bound to the database in anyway.
For example, it does not contain any GUIDs. This is because your Development and Live environments use different databases.

IMPORTANT: Custom configuration files must be stored on the file system and not in the database.

Sign up for our free beginner training. Boost your credentials through advanced courses and certification.
Register for Sitefinity training and certification.

Yes No

Your feedback about this content is important

How helpful is this article?

Very helpful Somewhat helpful Not helpful

How can we improve this article?(Optional)

Fix typos or links

Fix incorrect information

Add or update code samples

Add or update illustrations

Add information about...

Send feedback Cancel