G Guest Jan 29, 2007 #1 Does anyone use the My.Settings for runtime parameters? I.E. storing global variables? Is that proper?
Does anyone use the My.Settings for runtime parameters? I.E. storing global variables? Is that proper?
A AMDRIT Jan 29, 2007 #2 I use it for all of my runtime environment settings. It is proper because that is what MS implemented it for.
I use it for all of my runtime environment settings. It is proper because that is what MS implemented it for.
H Herfried K. Wagner [MVP] Jan 29, 2007 #3 Spam Catcher said: Does anyone use the My.Settings for runtime parameters? I.E. storing global variables? Click to expand... Settings are typically persisted when the application terminates and reloaded when the application starts, so if you want this behavior, use 'My.Settings'.
Spam Catcher said: Does anyone use the My.Settings for runtime parameters? I.E. storing global variables? Click to expand... Settings are typically persisted when the application terminates and reloaded when the application starts, so if you want this behavior, use 'My.Settings'.
G Guest Jan 29, 2007 #4 I use it for all of my runtime environment settings. It is proper because that is what MS implemented it for. Click to expand... OK, just checking because it seems that the My.Settings is more for "User Preferences" than runtime preferences. In anycase, it's a nice framework to use
I use it for all of my runtime environment settings. It is proper because that is what MS implemented it for. Click to expand... OK, just checking because it seems that the My.Settings is more for "User Preferences" than runtime preferences. In anycase, it's a nice framework to use