Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Host vs. Mod Developer on Full or Medium TrustHost vs. Mod Developer on Full or Medium Trust
Previous
 
Next
New Post
7/9/2006 8:00 PM
 

HELP!  I am trying to get a DNN site working and the premium modules that I purchased from Snowcovered won't work properly on my Hosted Site. 

The Host Says:

Dnn startard is Medium Trust, this is what we are using.
Please ask the developer if the module can run under ASP.net Medium Trust.

Could you ask the developer when DNN lowered the trust level to Full Trust? as far as we know Full trust is not recommended by NNN core team on shared hosting environment.

The Developer Says:

DNN has never lowered the trust settings to full - it was allways Full Trust, so no need to lower it.
Full trust is the default setting for DNN when it's delivered.
To set Medium Trust you have to change it explicitely and it takes conscious user action to do so.
Hosters usualy change trust in machine.config, not in web.config and it is not possible to foresee what changes they will make, as they vary wildly, as far as I know.
 
Therefore our modules are delivered as compatible with default DNN package, i.e. full trust..
They might work under customized trust settings, and again, they might not - depending on what changes are enforced.
 
I am New to DNN and this kind of infighting can't be good for anyone. Can someone please tell me who is right so I can have this issue resolved because it is clearly not going to be solved by me.

Thanks
 
New Post
7/9/2006 9:28 PM
 

Actually, DotNetNuke has been written so that it, and all the core modules we ship, could work in medium trust, since October 2004. We did this for a number of reasons :

1. Being able to run DotNetNuke in medium trust is a large security benefit.

2. Early indication from Microsoft was that they were going to make changes to asp.net 2.0 so that medium trust was a commercial possibility (in asp.net 1.1 you cannot use oledb sources such as MS access in medium trust - so many hosts distregarded it)

3. Hosters began to let it be known that they were being advised by Microsoft to run asp.net 2.0 app's under medium trust, so not making it possible to run dotnetnuke in medium trust would have restricted it's use in many cases.

We test and develop all core modules in medium trust (hence the reason for the development.config file, which indicates the developement settings we use), and also have to live with the restrictions (e.g. we've love to add lots of webservice support - but under medium trust suppport for webservices are limited, so we don't use them), and encourage all 3rd party modules to use medium trust, but it's up to them naturally what they use e.g. I developed a few modules that use the system.net libraries to do whois, ping and tracert requests, none of which work in medium trust, but as I use them for intranets, i can adjust the trust policy accordingly.

As for the statement "To set Medium Trust you have to change it explicitely and it takes conscious user action to do so.

Hosters usualy change trust in machine.config, not in web.config and it is not possible to foresee what changes they will make, as they vary wildly, as far as I know."
 
In my experience this is not true - the majority of major hosting providers such as godaddy, webhost4life, pipex etc. all set their sites to run in medium trust in their machine.config and deny users the ability to override it. IMHO module developers should indicate the trust level their modules require, particularly if they do not run in medium trust, which is not the effective default trust level for asp.net 2.0 applications in many of the worlds largest hosting organisations.

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Host vs. Mod Developer on Full or Medium TrustHost vs. Mod Developer on Full or Medium Trust


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out