.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

Deploying Branding Solutions for SharePoint 2010 Sites Using Sandboxed Solutions

Posted By:      Posted Date: April 10, 2011    Points: 0   Category :SharePoint
Learn to create sandbox-compatible branding solutions using custom master pages, CSS files, and images that can be deployed to SharePoint 2010 farms.

View Complete Post

More Related Resource Links

Sample: Deploying Branding Solutions for SharePoint 2010 Sites Using Sandboxed Solutions

Explore the code as you learn to create sandbox-compatible branding solutions using custom master pages, CSS files, and images that can be deployed to SharePoint 2010 farms.

SharePoint's Sandbox: Developing, Deploying and Monitoring Sandboxed Solutions in SharePoint 2010


The challenge in SharePoint development has always been the balance between creating and deploying solutions that you can trust not to damage or impair a SharePoint farm. A new feature in SharePoint 2010, called Sandboxed Solutions, enables farm administrators to feel comfortable that the SharePoint farm is safe, gives site collection administrators the authority to manage applications in their site collection, and provides developers with the flexibility to create solutions they know will be deployed in a safe and rapid manner.

Paul Stubbs

MSDN Magazine November 2009

Sandboxed Solutions for Web Parts in SharePoint 2010

SharePoint 2010 provides a new sandboxed environment that enables you to run user solutions without affecting the rest of the SharePoint farm. This environment means that users can upload their own custom solutions without requiring intervention from administrators, and without putting the rest of the farm at risk.

Chapter 4: Sandboxed Solutions (Inside SharePoint 2010)

Sandboxed solutions represent a new form of solution deployment and management in SharePoint 2010. Learn how these solutions balance agility with farm stability and are considered a best practice for SharePoint developers.

Video: SharePoint 2010: Introducing Sandboxed Solutions

Sandboxed Solutions are SharePoint Solution Package files (WSP files) that are limited in what they can do and in the server resources they can use. What they can do is limited using Process Isolation and Code Access Security limited to the SharePoint Site. The resources they can use are limited by process monitoring, logging and log aggregation. (Length: 14:42)

Video: Sandboxed Solutions in SharePoint 2010

This video provides an overview of sandboxed solutions in SharePoint 2010. (Length: 4:18)

Video: Web Parts in Sandboxed Solutions in SharePoint 2010

This module shows how to develop Web Parts for sandboxed solutions in SharePoint 2010. (Length: 4:51)

Video: Capabilities and Elements in Sandboxed Solutions in SharePoint 2010

This demonstration illustrates some of the allowed and disallowed operations in sandboxed Web Parts. (Length: 8:46)

Office Add-Ins: 3 Solutions for Accessing SharePoint Data in Office 2010


SharePoint 2010 introduces a number of new ways to access business data and present it to the user. We'll show you several options that range from no-code solutions to fully integrated Office add-ins.

Donovan Follette , Paul Stubbs

MSDN Magazine July 2010

Developer Training: Composite Solutions in SharePoint 2010

Discover how composite capabilities in SharePoint 2010 can be combined to provide desired functionalities. This training module covers new site-scoped workflows and tools, as well as the steps needed to write connectivity between SharePoint and external systems.

Redeploying Customizations and Solutions in SharePoint Foundation 2010 and SharePoint Server 2010

Learn how to redeploy customizations and custom solutions that you created for Windows SharePoint Services 3.0 and SharePoint Server 2007 in SharePoint Server 2010 and SharePoint Foundation 2010.

Module 8: Creating Silverlight User Interfaces for SharePoint 2010 Solutions

SharePoint 2010 integrates closely with Microsoft Silverlight to enable you to build compelling user interfaces that interact with SharePoint data.

Video: How to Build SharePoint 2010 Project Items, Features, and Solutions

This video describes how to build SharePoint 2010 artifacts with Visual Studio 2010. (Length: 2:17)

Video: SharePoint 2010 Solutions in Visual Studio 2010

This video demonstrates the tight degree of integration between SharePoint 2010 and Visual Studio 2010. (Length: 17:32)

Learning Snack for Developers: Developing Solutions with Microsoft SharePoint 2010

Five videos on SharePoint 2010 development made easy, creating a SharePoint 2010 solution, deploying a solution, Silverlight applications and the client object model, LINQ to SharePoint, and more.

Deploying and Using jQuery with a SharePoint 2010 Sandboxed Solution

If you're an avid reader of this blog, you probably now that I'm quite a big fan of the jQuery Javascript library, especially in combination with SharePoint sites. For a while I've been trying to find a mechanism to deploy jQuery and add a reference to it on all SharePoint pages of a site, by just using a Sandboxed Solution. The first part, deploying the jQuery file, is really easy; this can be done in a Module in a SharePoint project. The second part was more of a challenge; making sure the jQuery file got referenced in all pages of a SharePoint site. My initial thought was to do this by using the AdditionalPageHead Delegate control, but it's not possible in a Sandboxed Solution (you need to deploy the .ASCX to the SharePoint root). My second thought was to use the new ScriptSrc attribute you can use in a CustomAction (I wrote about this attribute some time ago). But initially I was under the impression that the ScriptSrc attribute could only target Javascript files loaded from the SharePoint Root (the \LAYOUTS) folder, resulting in a no-go for a Sandboxed Solution as well. Daniel McPherson stumbled upon this issue as well, but neatly solved it using Javascript to add the reference dynamically. But apparently you can make use of the ScriptSrc attribute to reference files from the Virtual File System (e.g. a Document Library in a site) as well! (thank you Frederic Dobon for men

Localize SharePoint 2010 Solutions


Hello everyone,

I`ve a SharePoint 2010 Solution with Custom Actions (xml), Application Pages (aspx) and of course Code behind (cs) files. What I`am trying to do is, to localize the whole Solution.

First thing I did is to add a Mapped Folder to 14\Resources and add my Resource Files in there. I could work with that in the xml and Code behind files but not in the aspx ones as the Resource Files where not copied to the AppGlobalResource Folder...

So I added an empty SharePoint Project and put my Resource Files in there. Afterwards I changed the Deployment Type to AppGlobalResource so the aspx files get the Resource Strings. But in this Scenario my xml files wouldn`t find them anymore and I can`t use SPUtility in the code behind files too.

How do I deploy Resource Files to SharePoint so they get copied to the 14\Resources Folder and the AppGlobalResource Folder and then be able to use the Resource Strings within all parts of my Solution?


Thank you for your help!

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend