Apr 12, 2013 at 8:59 AM
Edited Apr 12, 2013 at 10:15 AM
the trust specification. They've run that way since they were Mosso. They haven't published a 4.5 specific trust model, although maybe that's the same as 4.0.
I use them for nearly everything these days as they're much more reliable than any other of the mass hosting companies, and their support is good. They now know they don't support Orchard and so that will save other customers hassle. My experience with large
systems means I like things which are as locked down as possible.
Clicking the "documentation" button on this page shows text system requirements for use "full trust
" on the page there. However
the actual documentation for the install
doesn't mention this requirement. Perhaps that could be fixed.
I don't think Orchard should test hosters at all, although I disagree with the analysis in the linked ticket that limited trust is "no longer recommended" or that it's a good idea for shared hosts to allow more trust than's needed. But that's the
real world for ya. You can either support it or not, but Microsoft haven't provided the justification suggested at all.
Yet I can today run my test IIS server with Rackspace's config and that has no problems. Thinking about it, I first installed Orchard precisely as per the instructions (yeah, I read those, not the "documentation").
I installed the Rackspace limited trust config, once I knew how Orchard was structured. So my guess is that the problem is likely that it's logging the setup process (something I care nothing about, assuming it works), and that's what's failing
on Rackspace. If I can work out what precisely it is, then maybe I can cheat it that way, or hack log4net out of there or something.