User Options

juddaman posted on Friday, October 12, 2007

Hi all

I've just reworked my app as business code had creeped into the UI layer. I've come to a point where I need to move user options from a settings file to the DB.

So I'm thinking about creating a UserOptionsBO which allow user to maintain their options. Then I'll create a UserOptionsInfoBO with readonly properties so I can get the properties as needed.

What do you guys think of this somewhat standard method? How does it compare to the way you handle user options?

Cheers

George

ajj3085 replied on Friday, October 12, 2007

That sounds like a good plan, if all your options can be represented that way. 

Personally I use the .config file to store User level application settings.  But my options are mearly color preferences and such, nothign that actually changes how the application works.

juddaman replied on Friday, October 12, 2007

Hi Andy

I've been using .config too, and will continue to for Windows colour and sizes etc. The options I'm talking about are things like "grace period between work slots", "default project", "max number of active projects" etc, so BL properties (as you say properties that change how the app works). Thanks for the reassurance.

George