C#

string strType = "hello";

ApplyCleansingRulesFurther(ref strType, strIssued);

private void ApplyCleansingRulesFurther(ref string strType, string strIssued)
{ 
  if (strType.ToLower().Trim().Contains("hello there"))
  {
    if (strIssued.ToLower().Trim().Contains("yes"))
    {
       strType = strType.Replace("hello there", "Hello There!");
    }
  }
}

string type = "hello";

type = ApplyCleansingRulesFurther(type, issued);

private string ApplyCleansingRulesFurther(string type, string issued) { 
  if (type.ToLower().Trim().Contains("hello there")) {
    if (issued.ToLower().Trim().Contains("yes")) {
       type = type.Replace("hello there", "Hello There!");
    }
  }
  return type;
}

John Simmons / outlaw programmer wrote:

The app.config is a damn handy thing, and unless you have some fairly bizarre requirements, you should make use of it. The only bad thing about the app.config is that assemblies (DLLs) cannot easily have their own app.config.

User settings (settings that can be changed by the user) are stored in a user config file in the appropriate special (hidden) folder (ProgramData in Vista). Google "c# settings" or something like that to get an idea of using them, or even search CodeProject articles. I know there are at least three articles here that deal with user settings.

EliottA wrote:

how would you store user settings of an application?

John Simmons / outlaw programmer wrote:

I wouldn't use a singleton unless the boss told me to, or unless some other reason caused by the requirements or code forced me to do so.

hopingToCode wrote:

Is there a problem with it I should be aware of so I limit using it.