SPS development tip of the day


Tip of the day for developing under SPS-


If you get “Debugging is not supported under current trust level settings“ when trying to attach to the w3wp.exe process from VS, modify the following line in your web.config:


<trust level="WSS_Minimal" originUrl="" />   


change it to:


<trust level="Full" originUrl="" />


 


 

Comments (7)

  1. Kailas says:

    Works fine !! Thanks

  2. Yaron bs says:

    Hi Addy !

    Just wanted you to know that this tip seems to apply to scenarios where a custom web service is to be installed on the SPS machine as well. I’ve seen this mentioned on Google groups and here, and it actually worked for us, but I still need a better way since messing with the site-wide trust level is something I would like to avoid. Perhaps there is a way to change the existing trust levels to be more specifically generous towards this web service in particular (as it is when using the SPS object model from a web part)? I’ll check this out later (when a presentation is NOT imminent).

  3. Bryn says:

    Worked perfectly.

    Thanks!

  4. Eric Schmidt says:

    Thanks – this did the trick

  5. Flea says:

    This appears to be the recommended Microsoft Solution as well.

    See:

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;828810&FR=1

  6. Flea says:

    Allow me to correct my previous post. After further investigation, I have found a couple of other links that explain things a bit better and more clearly and will also address Yaron bs’s issue with granting full access:

    See:

    http://weblogs.asp.net/sbehera/archive/2004/06/08/150658.aspx

    and

    http://msdn.microsoft.com/library/default.asp?url=/library/en-us/spptsdk/html/smpscCodeAccessSecurityAdmin.asp

    HTH,

    Flea

  7. For detailed information on why this message is received, the following post is helpful. Net: setting trust level to Full is overkill.

    http://www.bluedoglimited.com/SharePointThoughts/ViewPost.aspx?id=60

Skip to main content