My web service needs to access classes from external assemblies. The names of the external assemblies are only known at run time. Because the external assemblies are not explicitly referenced by the web service at compilation time, they are not cached by IIS. The result is that these assemblies are left in the web service's root directory instead of being copied with the web service dlls.
I can access them directly from the web service's root directly (using Context.Server.MapPath), but then I loose that ability to modify the assemblies since they are always used.
Is there a way to add custom assemblies to the list of cached files at run time?