It's rather trivial to use xsd.exe to generate the schema and XmlSerializer to serialize / de-serialize the config values. Of course, a better approach like what you suggested would be nice :)
> -----Original Message----- > From: dotnet discussion [mailto:[EMAIL PROTECTED]] On 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 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 around that to parse the file, > define schema etc. > > The point I am trying to make is that why cannot dllhost.exe not provide a > scheme where it looks for a configuration file that corresponds to each > COM+ package. A la "deployment descriptor" xml file. aspnet_wp.exe the > other well CLR host seems to do it. > > Thanks, > > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
