Return to Answer

A few thoughts:

• The name "CustomizationHelper" is not very specific. How about CustomerBrandingService? Even though it "just" fetches data from a config file, that may not always be the case, and it is still an application service. (Naming classes with "Helper" is similar to naming with "Manager" - see reference on that below.)

Also, while your question is reasonable and simple, it is not clear to me what decisions you will make from this. For example, if this is the basis for a whole app, I suggest some other options to consider:

• Why are you building a WinForm app in 2011? Consider WPF or Silverlight (possibly Silverlight Out-of-Browser "SLOOB").

• If you choose WPF or Silverlight, the title would be assigned most naturally using Data Binding through the Model-View-ViewModel pattern.

Pointers for more information:

• How to avoid calling every class a "Manager" class

• Data Binding with WPF (Silverlight is very similar)

• The Model-View-ViewModel Design Pattern for WPF and Silverlight

A few thoughts:

• The name "CustomizationHelper" is not very specific. How about CustomerBrandingService? Even though it "just" fetches data from a config file, that may not always be the case, and it is still an application service. (Naming classes with "Helper" is similar to naming with "Manager" - see reference on that below.)

Also, while your question is reasonable and simple, it is not clear to me what decisions you will make from this. For example, if this is the basis for a whole app, I suggest some other options to consider:

• Why are you building a WinForm app in 2011? Consider WPF or Silverlight (possibly Silverlight Out-of-Browser "SLOOB").

• If you choose WPF or Silverlight, the title would be assigned most naturally using Data Binding through the Model-View-ViewModel pattern.

Pointers for more information:

• How to avoid calling every class a "Manager" class

• Data Binding with WPF (Silverlight is very similar)

• The Model-View-ViewModel Design Pattern for WPF and Silverlight