RickN said:
As I understand it, when a remoting application runs, it checks to see if it
has the most current version of the dll, if not it downloads it to the
download cache and then loads it from the download cache. So, as I
understand it, if it exist in the download cache, it isn't even going to
look in the application directory, as you suggest. I also understand that
files loaded from the cache must go thru a security check and files loaded
from the GAC, do not. Therefore, I don't understand why you say I would not
want to load from the GAC for performance reasons.
Please explain.
Thanks,
RickN
You are mixing together a number of different topics. This article explains
some of the issues.
http://msdn.microsoft.com/msdnmag/issues/02/07/NetSmartClients/
I did not state that you would not want to load from the GAC for performance
reasons, what I said was that performance by itself is not a sufficient
reason to put assemblies into the GAC. Files loaded from the GAC go through
a security check that same as any other assembly; all assemblies use Code
Access Security, it's just that assemblies in the GAC typically are granted
more permissions then assemblies downloaded from a website.
You asked was about copying files to the GAC - you cannot copy files there,
the files must be installed, and files installed into the GAC must be signed
with a strongname. The GAC is not the same as the download cache. The
download cache can be located anywhere, is usually unique per logged-in
user, and has no strongname requirements. The download cache can be cleared,
deleted, etc.; it is just a temporary repository - the GAC is permanent.
Signing assemblies has an effect on how versioning works. You should read up
on this and plan accordingly.
You indicated that you could run an installation program; this implies that
you could install your application anywhere onto the client's machine at
that time, so you could create a directory for your application and put your
assemblies into that directory - this is what I meant when I referred to the
application base directory.