After publishing the Windows AppFabric service from VS with web deployment, temporary cached DLLs that are still in use

Question

I have several Windows 2008 R2 AppFabric always running autoplay services deployed for this article . Services vary in type, some of them are Quartz.NET scheduled jobs, some are NServiceBus endpoints, and some are WCF web services. I am having problems deploying where, after publishing, services continue to use old DLLs. As soon as I stop the corresponding application pool and clean up "C: \ Windows \ Microsoft.NET \ Framework64 \ v4.0.30319 \ Temporary ASP.NET Files", the newly deployed DLLs will be used. If I did not clear this directory and restarted the application pool, sometimes I get the following error in the event log:

While processing a managed application, an error occurred during startup of the service for the configuration path: 'MACHINE / WEBROOT / APPHOST / services / products / importing.retrieval. an error message appears: "Initialization error trying to preload the application.

Exception: System.InvalidOperationException

Message: A well-known object of type "System.Web.Hosting.PreloadHost" already exists in this application domain.

StackTrace: at System.Web.Hosting.HostingEnvironment.CreateWellKnownObjectInstance (String assemblyQualifiedName, Boolean failIfExists) at System.Web.Hosting.HostingEnvironment.CreateWellKnownOejectItem.Ieb.Istem.Ieb.Istem.Ieb.Istem.Ieb.Industriefben.en Type of type, IApplicationHost appHost, Boolean failIfExists, HostingEnvironmentParameters hostingParameters) in System.Web.Hosting.ProcessHost.PreloadApplicationIfRequired (String appId, IApplicationHost appHostParameter, HostingEnvironmentParameters hostingParametersHostablePostmeters.ostablehostebpablemeter.contentpeb.processmeter.ableebebprocessprocessmeter.ableebebprocessprocessmeterlockableebebprocess_contentapeb.process_client.process_content.process > C_DisplayClasse.b_c (Object o) ". The workflow will be marked unhealthy and will be disabled. The data field contains an error code.

The error code points to this article , however this does not seem to apply.

Should I restart the application pool as part of the web publishing pipeline?

What can help to understand what happens to temporary data and the application pool when using web deployment.