Skip to main content

SharePoint 2010 : Sandbox Solution Part 1

Image
By

Sandbox Solution is similar to SharePoint Web Solution Package the difference this solution only deploys at the site collection solution gallery. It is activate by site collection owner. Sandbox Solution you get the restricted subset permission of SharePoint Object Model. 
  • SPUCHostService.exe :  Code runs under special monitored process called  SPUCHostService.exe
  • SPUserCodeWebPart : Web Part that loads the Sandbox Web part Called SPUserCodeWebPart Wrapper.
  • SPUCWorkerProcess.exe : Sandbox run under the worker Process called SPUCWorkerProcess.exe.  This is process you need to Attach for debugging.
  • SPUCWorkerProcessProxy.exe : Communication to the farm under full trust using SPUCWorkerProcessProxy.exe

We need Sandbox solution because:
  1. You don’t have a SharePoint Farm Permission but you still want to deploy the custom code in SharePoint this is only way to deploy the custom code in SharePoint.
  2. Hosted environment you want to deploy the custom code. Then only way to use sandbox solution to deploy custom code example. Office 365.
  3. Sandbox solution protects the farm to the bad code like unhandled exception, process intensive operation.
  4. SharePoint Farm Administrator increase or decrease your sandbox Quota. Also specific solution can be blocked by SharePoint Administrator.
  5. Site Collection Site Collection Quotas and Locks used for setting the Quota template or individual quota values for a Web site collection.
Sandbox works on partial trust application.

Special version of assembly used for Sandbox solution. The assembly lives under

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\UserCode\assemblies\ Microsoft.SharePoint.dll

Allowed feature Element
  1. ContentType
  2. Field
  3. ContentTypeBinding
  4. CustomAction
  5. Module
  6. ListInstance
  7. ListTemplate
  8. Receiver
  9. WorkFlowAssociation
  10. PropertyBag
  11. WorkFlowActions(Custom WorkFlow Actions)
Prohibited Feature Element
  1. Control
  2. Workflow
  3. CustomActionGroups
  4. Document Convertor
  5. FeatureSiteTemplateAssociation(Also Called Feature Stapling)




Labels:

Comments

Post a Comment

Popular posts from this blog

SharePoint RPC Protocols Examples Using OWSSVR.DLL

By
What is SharePoint RPC Protocols? Part 1 This reference includes information about the methods and usage of SharePoint Foundation Remote Procedure Call (RPC) protocol. This protocol can be used in Win32-based applications or in ASPX applications to make HTTP POST requests to the server. Methods in this protocol that do not modify the contents of the database can also be used in URL protocol to make HTTP GET requests. Definition taken from http://msdn.microsoft.com/en-us/library/ms448359.aspx You will find the OWSSVR.DLL in SharePoint 2010 Server Physical Path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI and MOSS C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\ISAPI OWSSVR.DLL List of commands DialogView  Display ExportList GetProjSchema GetUsageBlob HitCounter RenderView To read more about the OWSSVR.DLL command Please read the URL Protocol from Microsoft Blog having a URL http://msdn.microsoft.com/en...
1 comment
Read more

SharePoint 2013 Search Database Part 1

By
SharePoint 2013 Search architecture drastically change, as earlier in FS4SP 2010 we have 2 search applications “FASTContentSSA” and “FASTQuerySSA” and 7 total database in use. Following are the List of DB (FS4SP) FASTContentSSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTQuerySSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTSearchAdminDatabase : Fast Search Admin Database  In SharePoint 2013 search has only 1 Search Service application and 4 database in use. No property store database need any more, now the properties are directly stored inside the index component and all the index directly indexed to the physical system where FS4SP data comes from database as well as from the File system now data directly stored and indexed/ retried from the Physical disk because of this performance increase and search experien...
Post a Comment
Read more

STS CryptographicException Error : Key set does not exist

By
Common mistakes Both SharePoint Site and SSO Site NOT running on the same application pool. Application pool identity user doesn’t have permission to access the certification.  Solution to this problem Set the same identity pool to  : 2. Be sure to grant rights to the certificate for the App Pool running the web service Start -> Run -> MMC File -> Add/Remove Snapin Add the Certificates Snap In Select Computer Account, then hit next Select Local Computer (the default), then click Finish On the left panel from Console Root, navigate to Certificates (Local Computer) -> Personal -> Certificates You're certificate will most likely be here. Right click on your certificate -> All Tasks -> Manage Private Keys Set you're private key settings here. Add app pool account Reset iis
Post a Comment
Read more