Feature Scopes, targets, and security handling

Feature Scope (feature attribute) say where the feature will appear, and how activation/deactivation is inherited throughout the sites

- Web(subsite)
- WebApplication(web application)
- Site(site collection)
- Farm

Note: Farm features do not allow modules


DeploymentTarget (manifest.xml assembly attribute) lets us say we either want to give the dll full trust (stuck it in the GAC) or just copy it to the current web application's bin folder.

- GlobalAssemblyCache
- WebApplication



Save Control tagging to web.config lets assemblies execute code on our pages. This definition can, as the previous two ones, be compiled within the wsp package, in the manifest.xml.
<Assemblies>
<Assembly Location="mydll.dll" DeploymentTarget="GlobalAssemblyCache" >
<SafeControls>
<SafeControl Assembly="mydll, Version=1.0.0.0, Culture=neutral, PublicKeyToken=a3b8628163ff75bc" Namespace="mydll" TypeName="*" Safe="True" />
</SafeControls>
</Assembly>
</Assemblies>

http://weblogs.asp.net/soever/archive/2007/05/03/sharepoint-features-elements-scope-and-other-info.aspx

Comments

Popular posts from this blog

Mobile development opportunities

Breaking down document locking in SharePoint

Working around X-Frame-Options for iframes