Force reload signed assembly for windows service

[savajx1]

I am loading signed assemblies from a network share. The assemblies
are NOT INSTALLED in the GAC as they are part of an enterprise
distributed application implemented as a windows service that loads its
code (*.dlls/assemblies) from a network share. The assemblies are
signed to allow loading given code access security.

I am debugging the windows service but I cannot get it to
release/replace a copy of an old version of the *.dll. I even 1)
changed the assembly's version number; 2) reimported reference to it
into the windows service; 3) recompiled the windows service; 4)
replaced both the service *.exe and the new *.dll on the network share

Inspection of C:\Windows\assembly\download (which is evidently where it
stores references to its codebase) shows that it is still using the old
version of the assembly. This is confirmed when I try to run the code
as a) it still has the old behavior that I am trying to correct; and
b) it gives me the "classic" you are debugging using a source file that
is different from the running assembly message.

Does anyone no how to force .Net to use/load/replace the correct new
version of the assembly that currently resides on the network share?

The strange part is that it shows the correct path to the assembly but
shows the wrong version number. Using ILDASM I have confirmed that the
version that resides on the network share is the correct new version .