This project is read-only.

Assembly "Stuck" After Deploying

Topics: Installing Orchard, Troubleshooting
Jul 17, 2012 at 7:02 PM

We encountered a really odd bug in deploying an Orchard site, and the only way to fix it was to delete everything and set it up from scratch again.

In a nutshell, we had a module update to deploy, but in the enterprise environment we use only compiled assemblies are deployed. The previous version of the assembly wrote a log so we could tell exactly which assembly was being used by the runtime.

No matter how many times we deleted the module's bin and the App_Data/Dependencies folder, the old assembly kept being used by the runtime- and we couldn't even figure out where it was- even with the new assembly in the module's bin, we didn't see ANY corresponding assembly copied into App_Data/Dependencies. Yet, with apparently no runtime dll, the module still functioned, but using the old code.

I want to understand the dynamic compilation better, at least to the extent I can understand this behavior and prevent it from impacting future deployments.

Jul 21, 2012 at 1:33 AM

We never did really figure this out, we THINK what happened was a combination of assemblies and a few code files got pushed up to the server, and Orchard got "confused."- apparently favoring the code files for the compiled assemblies.