My company has a large number of clients, and we currently can process a limited number of clients per server. However, each client uses the same main web application. Currently, some content is stored locally on each site, so we cannot use them in the same site / application pool; although we have a multi-level conversion project.
We strictly sign all of our assemblies, and I thought it would be an interesting idea to see if we can get them to load the neutral domain into ASP.NET. The advantage of this would be to significantly reduce our memory costs, which is one of our highest cost / limiting factors at this time. In addition, it looks like we can optimize the deployment processes that are currently associated with IO / CPU compilation and quite often cost about 6 hours.
This task implies that I want to move assemblies from download to the application’s application domain to the common domain.
My understanding of the requirements for a neutral domain boot:
- The assembly must be strictly signed by the GAC.
- Dependencies in closing bindings must be in the GAC [and strongly signed].
I tried to get this to work, but I can't get it to work for a small sample application. I tried to put Newstonsoft.Json in the GAC first, and to my excitement, it moved to the shared domain after recompiling. However, I cannot get any of the others to switch to the common domain even after GACing all of them:
My goal is to get my main application DLL to load the domain neutral. How can I debug / move forward by figuring out why the rest of the assemblies do not load as neutral?
Also, I'm a little confused about how the codepage with the NGEN code relates, or differs from collections loaded by the common domain.
Joshua enfield
source share