Sharepoint : Sharepoint 2010 Execution Models Overview

Leave a comment

• The full-trust execution model. Assemblies are deployed to the global assembly
cache and non-compiled components are deployed to the server file system. The
solution runs using the same process and permissions as the SharePoint application
and is available to the entire server farm.
• The bin/CAS execution model. Assemblies are deployed to the bin folder for the
SharePoint Web application in the IIS file structure and non-compiled components
are deployed to the server file system. The solution runs using the same process as
the SharePoint application, but its permissions are restricted by the code access
security policy specified by the Web.config file. The solution is available to all sites
within the SharePoint Web application.
• The sandbox execution model. The solution package, including assemblies and
non-compiled components, is deployed to the solutions gallery in a site collection.
The solution runs using an isolated, low-privilege process. Sandboxed assemblies
have access to a restricted subset of the SharePoint API and are subject to significant
CAS restrictions. Access to system resources is monitored and throttled to
prevent adverse effects on the wider SharePoint environment. The solution is only
available within the site collection to which it is deployed and cannot access
resources from outside the site collection.
• Hybrid approaches to execution. You can extend the functionality of sandboxed
solutions by consuming various permitted full-trust components. You can develop a
full-trust proxy to expose functionality to the sandbox, you can consume full-trust
workflow activities from a declarative workflow deployed in a sandboxed solution,
and you can use external lists within sandboxed solutions to retrieve external data
through the BCS.

 

 

 

 

 

Advertisements

Sharepoint : Sandbox-compatible Visual Web Part

Leave a comment

Standard Visual Web Parts cannot be used in the sandbox because they require the deployment of ASCX files to the server. However, the Microsoft Visual Studio® 2010 Share-Point Power Tools provide an item template for a sandbox-compatible Visual Web Part.The sandbox-compatible Visual Web Part generates a source file from the user control and compiles this file as part of the assembly. This approach eliminates the need to deploy the ASCX file for the user control.

Enable Session State Sharepoint 2010

Leave a comment

Enable Session State is false in default configuration in Sharepoint 2010 .
To enable ASP.Net Session State in Sharepoint 2010 ,

1.Enter the following PowerShell command in the SharePoint 2010 Management Shell window:
Enable-SPSessionStateService –DefaultProvision
2.On each web application for which you want to use session state, edit the web.config file and set the enableSessionState property of the pages element as follows:
<pages enableSessionState=”true”