That will allow the config file to be downloaded from an ASP.NET web
site, but it won't fix the problem that custom config settings are not
available to the running application.

Chris Sells
http://www.sellsbrothers.com/

> -----Original Message-----
> From: dotnet discussion [mailto:[EMAIL PROTECTED]] On Behalf
Of
> Saurabh Nandu
> Sent: Friday, May 17, 2002 7:03 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [DOTNET] Rich client deployment over the web
>
> This solution was posted earlier by Mark(MS)
>
> And all you need to override this behavior is a simple web.config file
> in the vroot containing your exe:
>
> <configuration>
>     <system.web>
>         <httpHandlers>
>             <remove verb="*" path="*.config" />
>         </httpHandlers>
>     </system.web>
> </configuration>
>
> Make sure you don't put this in an ASP.NET app as anyone will be able
to
> download the web.config file which may contain sensitive information
>
> Regards,
> Saurabh Nandu
> [Microsoft MVP]
> www.MasterCSharp.com
> Master C#, the easy way...
>
> > -----Original Message-----
> > From: dotnet discussion [mailto:[EMAIL PROTECTED]] On
Behalf
> Of
> > Richard Case
> > Sent: Friday, May 17, 2002 2:25 PM
> > To: [EMAIL PROTECTED]
> > 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.

Reply via email to