1. The cache is a size limited LRU cache - when it hits the size limit you the cahce clears the oldest item - you can set the size in the admin tools
2. Put the config file in the same directory as the EXE on the web server. There are some caveats with this in V1: 1) ASP.NET by default does not allow the download of the config file - look thro' the archives for the fix ofr this 2) If you have auth on the web site the config file will not be correctly downloaded If you are using remoting you will need to modify the security settings for the app - by default remoting is not enabled for semi-trusted applications mark -----Original Message----- From: Teo Lachev [mailto:[EMAIL PROTECTED]] Sent: Friday, June 07, 2002 7:43 AM To: [EMAIL PROTECTED] Subject: [DOTNET] Windows Forms Web Deployment Questions I have the following questions about the Windows Rorms auto web deployment which is BTW very cool: 1. How long will an old version of the Windows Form executable and reference assemblies stay in the download cache? The auto deploy will automatically download the new versions of the assemblies, but what rules .net follows to scavenge the download cache? 2. If the windows forms application uses a config file, e.g. to specify remoting settings, will the config file settings be honored in the auto deploy scenario? Do I have to deploy the config file in the virtual folder as well, does it get downloaded to the client as well? 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.
