SharePoint 2010 introduces a new way of adding custom dev to SharePoint: Sandbox solutions, also called User Solutions. Solution deployment we are all used to in SharePoint 2007 still exists in SP2010 but those solutions will be called Farm solutions. Sandbox solutions are scoped to site collection and each site collection has its own gallery of these solutions which can be found in the site settings page.
Visual Studio 2010 gives visual tools to build the deployment package so long gone are the days of editing DDF and manifest files. After building the WSP you can upload it to the solution gallery just like you would upload a master page to its gallery. Select the solution you uploaded and the context sensitive ribbon gives you the option to activate the solution.
Sandbox solutions have their own advantages but also some limitations. Best part is you don’t have to deploy the solution from the server which means no server reset. You can do as many deployments as you want – every developer’s dream :) And, you can test your customizations in a test site collection on the production servers before applying it to the real sites.
Coming to the limitations, not every type of custom functionality can be packaged into a sandbox solution. From what I’ve seen so far any component that needs files in 14 hive cannot be part of sandbox solution, for e.g.: Visual Web Part
Happy Friday!
http://www.sharepointinnovations.com
Visual Studio 2010 gives visual tools to build the deployment package so long gone are the days of editing DDF and manifest files. After building the WSP you can upload it to the solution gallery just like you would upload a master page to its gallery. Select the solution you uploaded and the context sensitive ribbon gives you the option to activate the solution.
Sandbox solutions have their own advantages but also some limitations. Best part is you don’t have to deploy the solution from the server which means no server reset. You can do as many deployments as you want – every developer’s dream :) And, you can test your customizations in a test site collection on the production servers before applying it to the real sites.
Coming to the limitations, not every type of custom functionality can be packaged into a sandbox solution. From what I’ve seen so far any component that needs files in 14 hive cannot be part of sandbox solution, for e.g.: Visual Web Part
Happy Friday!
http://www.sharepointinnovations.com
No comments:
Post a Comment