n Behalf
Of
> Vishwas Lele
> Sent: Wednesday, April 24, 2002 11:27 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [DOTNET] Serviced Component and application.config
>
> Thanks for your response.
>
> The problem with using machine.config has to do with permissions.
> Administrators w
/02 10:26 PM
Subject: Re: [DOTNET] Serviced Component and application.config
Thanks for your response.
The problem with using machine.config has to do with permissions.
Administrators will not typically allow someone to add/update
appsettings
in that file.
I can certainly pass a file name as part
Just ran into this another approach suggested by Mike Woodring
http://www.develop.com/devresources/ResourceDetail.aspx?type=t&id=Per-
Assembly Configuration Files
You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.d
Thanks for your response.
The problem with using machine.config has to do with permissions.
Administrators will not typically allow someone to add/update appsettings
in that file.
I can certainly pass a file name as part of the constructor string but I
will need to build the scaffolding code aro
EMAIL PROTECTED]
> Subject: Re: [DOTNET] Serviced Component and application.config
>
> Vishwas Lele [mailto:[EMAIL PROTECTED]] wrote:
>
> > What is the recommended scheme to read configuration settings
> > when using Serviced Components (Server Package).
> >
> > Since
Vishwas Lele [mailto:[EMAIL PROTECTED]] wrote:
> What is the recommended scheme to read configuration settings
> when using Serviced Components (Server Package).
>
> Since dllhost.exe is going host for all the COM+ packages,
> using dllhost.exe.config file does not help.
>
> Is there a scheme sim
What is the recommended scheme to read configuration settings when using
Serviced Components (Server Package).
Since dllhost.exe is going host for all the COM+ packages, using
dllhost.exe.config file does not help.
Is there a scheme similar to aspnet_wp.exe where there is a web.config for
each v
