In the DNN installation guide, in the section "Configuring web.config for Installation," it says the following:

As with v3.x, before doing anything else rename release.config to web.config (if you
are required to run under Medium Trust then rather than use release.config, rename
development.config).

I'm using DNN 4.9 w/IIS7 ASP.NET 2/3/3.5, but I downloaded the older DNN 3.3.7 to see its development.config versus release.config, and there as well, I did not see any major differences. A comment in the file mentions that it is usually in machine.config. I'm curious why setting trust would be required at all for shared hosting if the hosting provider is already enforcing medium trust. I'm not sure why the web.config would need to specify this as well.

I was able to get DDN 4.9 to work with release.config and didn't need to deal with the trust setting so I was puzzled by these docs. Does anyone know if there's something I'm missing here?

Thanks,
Tom

Hi Steve,

Thanks for the info. I think I see why it's confusing as written (in the docs). I think what you're saying is that the target audience for the instructions is a developer, where the developer can use development.config to better test one's code in an environment that would otherwise be too free (full trust). I was reading it as development.config contains something that makes things work under a medium trust environment, and by examining the config file, I didn't see why it would be better to use development.config than release.config in a med trust env. I think the idea is that development.config is better to use in a full trust dev environment to be prepared for a medium trust production env. 

Let me know if I still am missing something here. Thanks for clarifying! Tom