Ent Application Blocks + Dev QA Production

Ent Application Blocks + Dev QA Production

• jbhatia

  I was thinking more along the lines of having one config file for all the environments and switch the mode to "Dev" or "QA" or "Prod". And then I was planning to have a MyAppConfigurationManagerFacade which will return getconnectionstring() depending on the environment its in. I couldnt get to make this kind of a facade to work with Enterprise Application blocks.
  

• Binu Jeesman

  Hi Indo,

  Whenever you have parameters which vary based on environment, you need to have them in either config file or a "reference data table" - except connectionstring - which will be in Config file anyway.

  Now for having config files - you can either maintain different config ( app.config) for different environment, or you can give appropriate dialogs in the setup/installer that you write to accept those parameters and edit the config file at install time.

  I have used both ways but have had greater success in maintaining different config files - it essentially reduces chances of error during installation.

  The practice I try to follow is to keep the app.config to real barebone - like having just the connection string, identity impersonate, timeout values etc. and to move all application specific parameters to some kind of a reference data table which I cache in memory at the load time ( using global.asax).

  You should be able to find design and code for maintaining such reference data as name value pairs - potentially saving you some time, though I would say Its quite simple to implement it.

  I am not sure whether the above is what you are asking - so if I misunderstood it completely - Can you please elaborate on the problem you are having

  Pranshu

  
  
  
• Ent Application Blocks + Dev QA Production