Can assembly caching be prevented when using the NTD scenario?

[Guest]

Is it possible to prevent caching of assemblies when using the NTD scenario (or at least have the cache cleared at the end of a user session)?

The reason I ask is that our team is currently developing a Windows Form based application and we plan to use the No Touch Deployment (Smart Client) features of the .NET Framework because of internal (business) limitations associated with permanantly installing code on client machines. We don't use incrementing version numbers associated with the Strong Name of the assemblies we deploy, again due to internal CM practices, and we find that without changing version numbers new "versions" of compiled DLL's don't get pulled down to clients because they are cached. Is there 1) a way to force a download into the cache without changing version numbers, or 2) clear the assembly download cache when a user session is complete (without GACUTIL)?

Thanks... Any guidance is appreciated.

Nick

 

[Guest]

We have found a work around for this if anyone is interested. I'm not sure if this is by design or not, but if you specify a codebase section in the application config file for the assembly then .NET always downloads the dependent assembly even though it may be cached in the assembly download cache.