SharePoint Brain

This post discuss about accessing public web services from sandboxed Silverlight application in SharePoint 2010. SharePoint 2010 introduced the concept of sandboxed solution where the application runs in separate process outside the w3p process where SharePoint is running. Sandboxed solutions having the restriction to make a call to external resources like database and web services. This restriction causing the SharePoint developers to access these resources from sandboxed applications. The solution is delivering a Silverlight application in sandbox environment which in turn calls the web service. Because Silverlight applications are running from the client machines even though they delivered from the sandbox solution. Once the application is available in client machine then they can call to the web services. This post shows calling the public web service and binding the results to SharePoint list. It also shows how to interact with SharePoint Client objects. we are using one of t...

The Three-state workflow tracks the 3 states in a list to manage the business processes. Example Three states for Issue List could be Open, Resolved and Closed. Three state workflow supports to track the list item or issue through states. The workflow assigns a task to a person and sends an email to that person. When workflow is completed it updates the status of the item or issue. By default Three-state workflow works with the Issue Tracking list template. To use the Three-state workflow, you must define a list to use the workflow and it must contain some items. Two options to use the 3 state workflow Create a Issue-Tracking list which is having 3 state workflow Create a custom list to use the workflow Creating an Issue-Tracking list with 3 state workflow 1. In Team site, All site content page , click create 2. In the create dialogue, click Issue-Tracking and type a name for the list 3. Enter the description for the list as shown below Create a custom list and add a...

Migration steps from MOSS 2007 to SharePoint 2010 System Requirements For migration from MOSS 2007 to SharePoint 2010 the minimum requirement is WSS SP2 and Office Server SP2 must be installed in the MOSS 2007 server. So before upgrade the content database make sure both the things are installed in the source server Preupgrade check Preupgradecheck command will let us know about the things that may restrict us to upgrade the database in SharePoint 2010 server. Before upgradation we need to fixed up all the steps which are failed in the preupgradecheck. Backup Content Database of MOSS 2007 site Before start taking backup of the database first go to the Manage Content Databases section in the Central Administration site and check the name of the database attach to your site. Central Administration  Application Management->Manage Content databases Open SQL Server right click on the database  Tasks  Back Up Click on Add button and browse to the path where you want ...

Sometimes JavaScript doesn't works in Modal DialogBox. Sample Code for Working under Modal DialogBox in Javascript Close & Next. 1. Add Page Header in Page Load Event Page.Header.Controls.Add(newLiteralControl(@"<base target=""_self"" />")); 2. Call JS Function on Close Click Response.Write("<scriptlanguage='JavaScript'>window.close();</script>"); 3. Call JS Function on Next Click Response.Redirect("Page.aspx", true);