>But I would HIGHLY avoid to have different behaviour, depending from the environment where your library lives in.
I eventually decided that it was not really the decision of the (rather general purpose) library to change its behaviour. I will strive to keep the library blind to how it's being called and let the parent application make such decisions. It turns out I could configure the behaviour in the config file anyway. I did not at first consider the loaded assemblies to be reliable. However, in hindsight, the entry assembly could be a good clue (but I haven't tried the different combinations to see what you get). Greg
