I cannot release a patch since there is nothing wrong in mojoPortal that I am aware of. No fault in mojoPortal has been identified.
mojoportal does not require 32 bit enabled and does not require it disabled. I only pointed out that someone else had a recurring problem in the same hosting when 32 bit was enabled.
I have no idea why the problem is happening. Many many others including myself use the exact same packages without any error.
changing settings like 32 bit on the application pool does force the application to restart and re-compile, and that may resolve an error for a while.
my advice is disable 32 bit since it is not needed by mojoportal and some people get errors in the same hosting with it enabled, and making that change may resolve the problem at least for a while.
errors that happen down in the windows/temporary aspnet files are outside the control of mojoportal code and more related to the asp.net compiler and server configuration, though it can also be caused by missing or mismatched set of deployment files. generally if I encounter an error down there I stop the web site. delete those temporary files and restart the web site so that aspnet can re-compile clean. stopping the iis web site is required because the files cannot be deleted while they are in use.