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.

Increase your Sitefinity skills by signing up for our free trainings. Get Sitefinity-certified at Progress Education Community to boost your credentials.

Get started with Integration Hub | Sitefinity Cloud | Sitefinity SaaS

This free lesson teaches administrators, marketers, and other business professionals how to use the Integration hub service to create automated workflows between Sitefinity and other business systems.

Web Security for Sitefinity Administrators

This free lesson teaches administrators the basics about protecting yor Sitefinity instance and its sites from external threats. Configure HTTPS, SSL, allow lists for trusted sites, and cookie security, among others.

Foundations of Sitefinity ASP.NET Core Development

The free on-demand video course teaches developers how to use Sitefinity .NET Core and leverage its decoupled architecture and new way of coding against the platform.

Was this article helpful?