Configuration Nightmare

[Guest]

Hi

I've been stumbling with this problem for several days, trying to have a
simple approach to my application configuration. Essentially my configuration
is as follows:

Install Folders
1) \MyApp
2) \MyExe1
3) MyExe1.config
MyExe1.exe
4) \MyExe2
5) MyExe2.config
MyExe2.exe

At (1) I have a snap-in.dll which is able to load the .config files for the
MyExe applications using ExeConfigurationFileMap and
OpenMappedExeConfiguration methods.

In the .config are custom configuration section handlers, but because the
ApplicationBase location is pointing to \MyApp folder (the location of the
snap-in dll), I get exceptions whereby the type of the custom section handler
can not be loaded - it's sitting down in the \MyExe1 or \MyExe2 folders.

If you are able to provide any insights as to how I can work around this, I
would be most greatful.

 

[sloan]

http://www.eggheadcafe.com/articles/20041204.asp

Check out Peter's code for a windows service.

You're not as interested in.... the msmq or command pattern, but rather how
he deploys different dll's with their OWN config files.

I added some functionality to one of his libraries as well, you'll have to
search the forum for it.