Sandman
Thu Mar 17 10:49:08 CST 2005
JF:Thanks for the link and thequote.
My next questions would be:
Is this still a problem in .Net v2.0 (looks like it is) and
Is this a bug or just how things are?
"JoeFusion" wrote:
> I've not been able to get this working either.
> from
>
http://msdn.microsoft.com/library/default.asp?url=/msdnmag/issues/02/07/NetSmartClients/toc.asp
>
> "Once the .config file has been cached, the .NET v1.0.3705 assembly resolver
> will not ask for it again, even if there is a newer version on the server.
> Unfortunately this means that you'd better be darn happy with your
> application's .config file because the client's Internet cache must be
> cleared before the .config file will be downloaded again."
>
> My workaround is to use a webservice, has the advantage of being able to
> change the settings for all users during runtime.
>
> "Sandman" wrote:
>
> > I'm deploying a windows form application using no-touch deployment and
> > Rockford Lhotka's NetRun app. The first time I run the app everything is
> > fine, the config file downloads to the client.
> >
> > But, if I edit the .config file on the IIS server (running MS Server 2003,
> > .Net Fw 2.0), the client doesn't download the new version the next time I run
> > the app.
> >
> > I checked the output of fuslogvw and it says the config file is from the
> > user's temp internet file directory. Its almost like if IE finds the file in
> > the temp dir, it doesn't even bother to check the server for updates.
> >
> > Any Ideas?
> >
> >