This would allow User B to update her default parameter values (to match User A's) without having to manually change them in the application (i.e., Edit Between Sessions). Subsequently, that user wants to share that modified configuration file with his team (via version control repository, for example, or email). That change needs to persist for all future sessions for that user (i.e., Edit at RunTime). User A starts up the model and decides to change the value of several of the parameters. I have a computational model with a config file that contains the default values for parameters in the model. [ BETTER Use Case: (In response to comments) Am I missing something? Is there another alternative that I am not aware of? But when using the built-in C# persistence mechanisms provided by ttings, I must choose at most 2 out of the 3. What I'm saying is that I want to be able to change a default setting at Design-time, at Run-time, or in-between sessions (i.e., by editing a config file). POTENTIAL WORKAROUND: Is there anyway to change the default storage location for the User Settings config file into a non-hidden folder? I understand that this could cause problems for users who share the same machine. Surely there must be some sort of mechanism that provides both functionalities.īOTTOM LINE: Why can't Application Settings ( ) be edited at Run-Time? That would solve all my problems. config file they should also be able to make a change at run-time that persists across settings (as can be done with User-scoped settings). However, the user shouldn't be forced to edit a. #Ampps setup code#Is there any "built-in" settings functionality that will allow me to edit settings by all three mechanisms? One of the primary motivations for using a configuration file is to allow users to change default values without re-building the source code (as can be done with Application-scoped settings). User | ttings | () | *Not supported*Īpplication | ttings | *Not supported* | edit SCOPE: | EDIT AT DESIGN-TIME: | EDIT AT RUN-TIME: | EDIT BETWEEN SESSIONS: The following table demonstrates the differnce: In C#, Application Settings are divided into two different types or scopes ("Application" and "User"), but both have limitations in regard to how they can be changed or modified. If I understand Application Settings correctly, I am limited as to when I can change/edit settings. NET configuration settings feature is not as flexible as I would like.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |