We have a plug-in system in the WCF service that checks the libraries located in the bin folder for specific build-level attributes and loads them. This allows you to configure specific calls based on which client makes the call. This works great most of the time. However, sometimes it seems that it will lose the dll, which causes the service to return to the default implementation for each client. So far, the solution has been to simply move the dll file from the bin folder and back. This causes asp.net to take the file, and the settings start working again.
I am at a loss as to why the assembly was skipped through this after a certain time. Any ideas as to what could be causing this?
Edit: The problem is more clearly worded.
Our services use the factory service to issue custom implementations based on which client calls the code. If there is no special implementation, we pass the default implementation. We use GetAssemblies to test assemblies that are decorated with an attribute that designates them as a custom implementation, and associates them with the client. The problem is that GetAssemblies stops returning the client assembly, although the library remains in the bin folder. Moving the dll from the hopper and back to it will fix the problem for about a week, until it repeats.
source
share