Aha! MarkB helped me figure out a work-around. To enable up-to-date access to an href-exe's config file, including custom sections, you need the following:
1. Enable anon access for the vdir via IIS config. 2. Use a web.config to allow .config files to be served [1] even if it's not an ASP.NET application. Neither of these make sense to me, but they do work. Chris [1] <configuration> <system.web> <httpHandlers> <remove verb="*" path="*.config" /> <add verb="*" path="web.config" type="System.Web.HttpForbiddenHandler"/> </httpHandlers> </system.web> </configuration> >Actually, the config file *has* been downloaded, but so far I haven't been >able to get the custom config sections out of it either. I think it's a ><gasp!> bug. The work-around is to do an HTTP GET manually to pull down the >config file and pull out the appropriate XML sections manually. This will >also work around the "opportunity for improvement" where the config will >only download once, even if it's been changed. > >Chris > >----- Original Message ----- >From: "Richard Case" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Friday, May 17, 2002 1:54 AM >Subject: [DOTNET] Rich client deployment over the web > > >> Hi All, >> We are looking to deploy our rich client app over the web. The download >of >> the assembly into the download cache and the showing of the form works >fine. >> Along with the app we have got a configuration file (also contained in the >> virtual directory of the webserver) that holds configuration settings. >When >> the application that has been downloaded to a remote machine tries to >access >> the configuration file it doesn't get the setting requested. I assume this >> is because the configuration file hasn't been downloaded. Does anyone know >> how I can make sure the configuration file is downloaded along with the >> assembly? >> >> Thanks, >> Richard You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.