Comments on: Code Access Security policy template for Visual Studio 2010 SharePoint Developer Tools

By: Waldek Mastykarz

Waldek Mastykarz — Wed, 22 Jun 2011 04:26:39 +0000

@Alex: You should be able by adding a custom CAS policy to your Package and configuring permissions for the WebService. This article might help you find out which permissions your assembly requires exactly: http://blog.mastykarz.nl/working-easier-custom-cas-policies/.

By: Alex

Alex — Tue, 21 Jun 2011 16:16:22 +0000

I've got an assembly that workd perfectly well if I set my app trust level to "Full" but I don't want to do that, I'd prefer setting only my assembly's trust to full, is that possible? the problem I have is that this assembly call webservice, any url could be entered. I tried adding this to my package.template.xml file but it didn't work :

By: Vasu K

Vasu K — Wed, 11 May 2011 03:04:40 +0000

We created a custom workflow and associated it with a document library. This works fine when I make "Trust Level" to "Full" in the web.config file. We kept "Trust Level" to "WSS_Minimal" in web.config file and created a "Code Security Access (CAS)" policy and added to the workflow project's "Package Manifest" as described in this post.

We are getting "Failed to Start (retrying)" error now and workflow is not starting.

Here is the CodeAccessSecurity that we used:

Can you please let us know if we need to make changes to the above CAS policy to make the workflow work?

By: Waldek Mastykarz

Waldek Mastykarz — Thu, 03 Mar 2011 14:31:02 +0000

@Oliver: The CAS policy that I provided is basically a starting point. Depending on what you're doing you might need to extended it with additional permissions, and elevating privileges is an example of this. When calling RunWithElevatedPrivileges in your code you need to add the Impersonate attribute (http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.security.sharepointpermissionattribute.impersonate.aspx) to your SharePoint Permission in CAS (Impersonate="true"). With that everything should work okay.

By: Oliver

Oliver — Mon, 28 Feb 2011 17:51:19 +0000

Hi Waldek,

I read your blog post about how to add CAS policies to a sharepoint 2010 solution with Visual Studio 2010. Really very informative :-)

At the moment I'm working on a little sharepoint 2010 webpart where I added a methode that uses RunWithElevatedPrivileges.
I need to add CAS policies to that webpart project – so I added the policies I copied from your post.
That worked fine until my code calls the method with RunElevatedPrivileges. In that case a security exception is thrown telling me that there is something wrong with aquiring policies from .
But I already added this to my CAS policies (like you've done).
I'm really stuck now – what policy do I need to added when using RunWithElevatedPrivileges?
Although I'm not a newbie to sharepoint development – I'm a newbie to using CAS. So I really would appreciate to get some help from you.

Regards,
Oliver

By: Waldek Mastykarz

Waldek Mastykarz — Thu, 27 Jan 2011 08:35:51 +0000

@Jos: great to hear it's working. You're welcome :)

By: Jos van Putte

Jos van Putte — Thu, 27 Jan 2011 08:15:09 +0000

@Waldek: I found it.. I started a new solution (empty) and added a new item to it from the solution explorer. There were the new items from the power tools..
Thnaks for your help.

By: Waldek Mastykarz

Waldek Mastykarz — Thu, 27 Jan 2011 07:41:23 +0000

@Jos: Did you install Visual Studio 2010 SharePoint Power Tools? There are other Power Tools as well so you have to check the ones you've got are the ones for SharePoint.

By: Jos van Putte

Jos van Putte — Thu, 27 Jan 2011 07:32:44 +0000

Thank you. I thought it was a security problem..
(Sorry for the duplicate messages)

I found the power tools and installed them but it is still not possible to create a sandboxed visual web part project.

By: Waldek Mastykarz

Waldek Mastykarz — Wed, 26 Jan 2011 16:15:37 +0000

@Jos: As the error says, you cannot deploy ASCX to CONTROLTEMPLATES in a Sandboxed Solution. Instead, you should be using the Visual Web Part Sandboxed that ships with the Visual Studio 2010 SharePoint Power Tools.