Custom Configuration File
What is the best practice for creating a custom configuration file (not persisted to the database) with no UX? I've been scouring the documentation, but it's not very clear if any of the paths I'm taking are correct.
My specific needs will be creating a configuration file within a custom module, where I can pull settings but not expose them to administrators.
Note: My default (.NET) thought would be to toss an app config in the module and manage it through the normal setting manager, but I want to learn the "Sitefinity way" for these things whenever possible.
Thanks!
Christian,
I wrote a blog post about configuration files in Sitefinity. See if this helps.
Let me know if this helps.
Craig