Re: No Touch Deploy Caching Issues

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Nick L. (NickL_at_discussions.microsoft.com)
Date: 08/02/04 

Date: Mon, 2 Aug 2004 10:25:06 -0700

Have you specified codeBase sections for your dependent assemblies in you app.config file? I have found that if I do then the dependent assembly is always downloaded. I'm not sure if this is by design or not, but for me it works nicely because I want to prevent caching of some dlls.

"Mickey Williams" wrote:

> Are you sure that they're being downloaded? NTD typically is fairly slow.
> The only way to know for sure is to use YATT or something similar. If you
> see that it is being downloaded, check to see if the HTTP-GET restricts the
> request to a specific date with the if-modified-since header.
>
>
> --
> Mickey Williams
> Author, "Microsoft Visual C# .NET Core Reference", MS Press
> www.servergeek.com/blogs/mickey
>
>
>
> "Paul Hetherington" <pNhOetShPeArMington@vNiOsSuPaAlMstatement.com> wrote in
> message news:Ot0lA3cPEHA.3328@TK2MSFTNGP09.phx.gbl...
> > Hi,
> > We have a NTD application that consists of a relativly small exe (100kb)
> > that access and downloads a variety of larger dlls as needed (some are as
> > large as 2mb). According to MS Documentation these dlls should be cached
> my
> > IE and only re-downloaded if newer versions are found no the server.
> > Through testing though we have found that these files actually get
> > re-downloaded every time the NTD application is launched from a new
> instance
> > of the IE Browser. If IE isn't shut down the caching works, but as soon
> as
> > IE closes and is restarted all of the dlls get re-downloaded.
> > Has anyone figured out a solution to get around this? This is causing
> major
> > headaches with the clients who don't understand why it takes so long to
> > start the application each time.
> >
> > TIA
> > --
> > Paul
> >
> >
>
>
>