Re: Client not recognizing updated assemblies on the web server

I do this in the launcher assembly:

                Dim formAsm As [Assembly] = [Assembly].LoadFrom(assemblyFile)
            Dim formtype As Type =
formAsm.GetType("CustomDataSystems.AMNET.Forms.AMNETMainForm")
            Dim FormObj As Object
            FormObj = Activator.CreateInstance(formtype)
            Dim Form1 As Form = CType(FormObj, Form)
            Form1.Show()

I also add a handler:

AddHandler _currentAppDomain.AssemblyResolve, AddressOf
MyResolveEventHandler

 Private Function MyResolveEventHandler(ByVal sender As Object, ByVal args
As ResolveEventArgs) As [Assembly]
        Dim simpleName As String = args.Name.Substring(0,
args.Name.IndexOf(","))
        Dim httpAddress As String = "http://"; & Me.URL
        Return [Assembly].LoadFrom(httpAddress & simpleName & ".dll")
 End Function 'MyResolveEventHandler



-----Original Message-----
From: Discussion forum for developers using Windows Forms to build apps
and controls [mailto:DOTNET-WINFORMS@xxxxxxxxxxxxxxxxxxx]On Behalf Of
Philip Sayers
Sent: Friday, February 27, 2004 10:46 AM
To: DOTNET-WINFORMS@xxxxxxxxxxxxxxxxxxx
Subject: Re: [DOTNET-WINFORMS] Client not recognizing updated assemblies
on the web server


Hmm...

You've got me stumped.

Is there anything in the IIS logs that may indicate what's going on.

Eg, where is the assembly.loadfrom probing to find the assemblies it
needs to download, is it looking in the right place?



-----Original Message-----
From: Discussion forum for developers using Windows Forms to build apps
and controls [mailto:DOTNET-WINFORMS@xxxxxxxxxxxxxxxxxxx] On Behalf Of
Greg Robinson
Sent: Friday, February 27, 2004 9:17 AM
To: DOTNET-WINFORMS@xxxxxxxxxxxxxxxxxxx
Subject: Re: [DOTNET-WINFORMS] Client not recognizing updated assemblies
on the web server

launcher that uses assembly.loadfrom()

-----Original Message-----
From: Discussion forum for developers using Windows Forms to build apps
and controls [mailto:DOTNET-WINFORMS@xxxxxxxxxxxxxxxxxxx]On Behalf Of
Philip Sayers
Sent: Friday, February 27, 2004 9:11 AM
To: DOTNET-WINFORMS@xxxxxxxxxxxxxxxxxxx
Subject: Re: [DOTNET-WINFORMS] Client not recognizing updated assemblies
on the web server


Is the app entirely ntd? Or do you have a launcher that uses
assembly.loadfrom()
?


-----Original Message-----
From: Discussion forum for developers using Windows Forms to build apps
and controls [mailto:DOTNET-WINFORMS@xxxxxxxxxxxxxxxxxxx] On Behalf Of
Greg Robinson
Sent: Friday, February 27, 2004 9:07 AM
To: DOTNET-WINFORMS@xxxxxxxxxxxxxxxxxxx
Subject: Re: [DOTNET-WINFORMS] Client not recognizing updated assemblies
on the web server

I have noticed this 'time span' thing too.  Although, I did an update
yesterday afternoon and one user today still did not get the update.
This
makes me nervous as I do not plan to install the sdk on every client
machine
so I can run gacutil.

-----Original Message-----
From: Discussion forum for developers using Windows Forms to build apps
and controls [mailto:DOTNET-WINFORMS@xxxxxxxxxxxxxxxxxxx]On Behalf Of
Philip Sayers
Sent: Friday, February 27, 2004 9:05 AM
To: DOTNET-WINFORMS@xxxxxxxxxxxxxxxxxxx
Subject: Re: [DOTNET-WINFORMS] Client not recognizing updated assemblies
on the web server


I've seen this before, and never really found out the exact cause...but

If I access the app from a machine that has never used it, I get the new
release of it.

If I go back to the client machine that has the older version and wait a
long time.. (like a few hours) and then access the NTD app, I get the
newer version.

I don't know how the ntd auto update system compares date/times to
determine what's newer.  Maybe it only compares to a resolution of a few
mins... maybe 10 min intervals.... maybe the problem is that the IIS
session from the original run of the app has to expires so that a new
request for the app causes iis to start a new session and serve the new
app.

I seem to remember something in the docs that talk about asp.net, where
if you updates the files in the web app folder, any currently connected
clients will continue to be served the older version, but new clients
get the new release..(the whole side by side execution docs maybe)

Can anyone else explain this?
Phil


-----Original Message-----
From: Discussion forum for developers using Windows Forms to build apps
and controls [mailto:DOTNET-WINFORMS@xxxxxxxxxxxxxxxxxxx] On Behalf Of
Greg Robinson
Sent: Friday, February 27, 2004 8:41 AM
To: DOTNET-WINFORMS@xxxxxxxxxxxxxxxxxxx
Subject: [DOTNET-WINFORMS] Client not recognizing updated assemblies on
the web server

We have a NTD WinForms app.  Our assemblies reside on our internal web
server.

I am noticing cases where an assembly is rebuilt and copied to the web
server, overwriting the existing one, and the client does not get the
updated assembly in it's download cache (the next time the client app is
started).  In those cases I have to run the gacutil to clear out the
client's download cache.  Then it works.

This does not happen all the time though.  Our assemblies are strong
named.
The timestamp does change.  So, why is the client still using the old
assembly in its download cache in some cases?


Greg Robinson
Custom Data Systems, Inc.
www.cds-am.net