All of the configuration needs to reside in the config file for the exe.
When you are developing, they are in different project folders, but when it
is deployed, they are all in one folder and the exe provides the config as
well as the policy file.
I remember scratching my head over this in WSE 2 when I first started using
it in a solution that had many projects and I was configuring the wse
properties for the individual projects that were class libraries.
So just do all of your wse 3 settings on the main exe project
Make sense?
julie
> Hi,
> I have a scenario as follow:
[quoted text clipped - 16 lines]
> Thanks
> KDV
KDV - 15 Feb 2006 14:03 GMT
I understand your point. I can make it work by putting all settings in main
exe file. That is how I am doing now (for time being). But let us assume that
I want to use third party DLL (Or I have to develop a DLL to be used in other
projects) which provides access to database. Only DLL knows whether to look
in the local database or access a webservice. So that means if I have to use
that DLL then I have to copy/paste all the settings from the third party dll
config file and put it in my main exe file. This seems a bit odd and destroys
the encapsulation concept.
But my concern is to confirm if it is possible or not to create some sort of
link between main exe config and my custom config file so that main exe just
point to the secondary config file and let WSE know where to look for
settings. (Just like I can put a file attribute in appSettings settings to
load settings from other file)
Just to know if it is possible or not. If not then I have no choice.
Tomorrow when I have to use more DLLs each is accessing a web service of diff
kind then it will be messy.
See, I can add web reference in DLL projects and it does its job(Then for
WSE settings I have to go to caller application config file. A bit odd)
Thanks
KDV
> All of the configuration needs to reside in the config file for the exe.
> When you are developing, they are in different project folders, but when it
[quoted text clipped - 31 lines]
> > Thanks
> > KDV
Julie Lerman - 15 Feb 2006 14:59 GMT
I know in a web app that if you have sub directories with their own
web.configs, they will take precedence over the parent config. I wonder
what would happen if you put the dlls in a subfolder with their own
app.configs and policy file. This is just grabbing at straws as I haven't
done this and do not have time to experiment. The main exe will have to know
how to find that assembly to. Just an idea. But I do not have the personal
knowledge to advise you on this.
julie
>I understand your point. I can make it work by putting all settings in main
> exe file. That is how I am doing now (for time being). But let us assume
[quoted text clipped - 70 lines]
>> > Thanks
>> > KDV
KDV - 15 Feb 2006 15:58 GMT
I think WSE should apply settings on fly. Not at the time the AppDomain is
loaded. I can even change in AppDomain where to find config file but that
will allow only one time and only one entry. So the idea is that WSE runtime
should look for the settings in the calling assembly config file (Calling
assembly for WSE runtime could be DLL or EXE) but not what is stored in
AppDomain
I will be more than happy and thankful if anybody can tell if there is any
possiblility or not.
Thanks
KDV
> I know in a web app that if you have sub directories with their own
> web.configs, they will take precedence over the parent config. I wonder
[quoted text clipped - 80 lines]
> >> > Thanks
> >> > KDV