The download cache is only used for shadow copy files if you don't
explicitly specify the CachePath when you set up the AppDomain. I'm pretty
sure this is how ASP.Net keep its stuff out of the dl cache.

-Ethan
-----Original Message-----
From: Keith Hill [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 21, 2002 7:49 PM
To: [EMAIL PROTECTED]
Subject: Re: [ADVANCED-DOTNET] GAC Download Cache


On Fri, 21 Jun 2002 09:26:26 -0700, Keith Hill <[EMAIL PROTECTED]>
wrote:

>So what if you do an Assembly.LoadFrom() on a local file path, say
>@"c:\temp\foo.dll"?  Could that throw the DLL into the download cache?

So a simple experiment indicates that is not enough. However, I did find
out that if you do this in an AppDomain who has had SetShadowCopyFiles()
called on it, then anything loaded via Assembly.LoadFrom() gets put into
the user's download cache.

--
Keith

You can read messages from the Advanced DOTNET archive, unsubscribe from
Advanced DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.


------------------------------------------------------------------------------
This message is intended only for the personal and confidential use of the designated 
recipient(s) named above.  If you are not the intended recipient of this message you 
are hereby notified that any review, dissemination, distribution or copying of this 
message is strictly prohibited.  This communication is for information purposes only 
and should not be regarded as an offer to sell or as a solicitation of an offer to buy 
any financial product, an official confirmation of any transaction, or as an official 
statement of Lehman Brothers.  Email transmission cannot be guaranteed to be secure or 
error-free.  Therefore, we do not represent that this information is complete or 
accurate and it should not be relied upon as such.  All information is subject to 
change without notice.

You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced 
DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.

Reply via email to