SharePoint Development ================== What are WebParts? Working with WebPart through browser Customize WebPart through SharePoint Designer Customizing List views (Conditional formatting) Create Webpart using Visual Studio Building a simple webpart Building a visual webpart Sandbox solution overview Farm Solution Deployment

1. MJ Ferdous
SharePoint Architect
Founder, SharePoint Expert Community

3. SharePoint Development
– What are WebParts?
– Working with WebPart through browser
– Customize WebPart through SharePoint Designer
• Customizing List views (Conditional formatting)
– Create Webpart using Visual Studio
• Building a simple webpart
• Building a visual webpart
– Sandbox solution overview
– Farm Solution Deployment

4. What are WebParts?

5. WebParts through browser

6. DEMO
Working withWebParts through browser

7. WebPart through SP Designer
Customizing List View
(Conditional Formatting)

8. DEMO
Customizing WebPart through Designer
Customizing List views (Conditional
formatting)

9. Create Web Part using VS
• Write your first custom web part for your SharePoint Site
– Create a new Visual Web Part Project from VS2010 Project
Template under SharePoint Category
– Define Project URL and Validate
– Deploy as farm solution {Default}
– Add Label and put the following code in the Pageload
• lblSiteName.Text = SPContext.Current.Web.CurrentUser.Name;
– Deploy solution
– Add this custom web part at SharePoint Site
– Deploy folder at C:Program FilesCommon FilesMicrosoft
SharedWeb Server Extensions14TEMPLATEFEATURES

10. DEMO
Build a custom web part using vs2010 and deploy
at SharePoint site

11. DEMO
Create a Visual web part

12. Source Code
• <SharePoint:SPDataSource ID="ProjectEstimationList" runat="server" DataSourceMode="List"
• SelectCommand="<Query><OrderBy><FieldRef Name='TaskTitle' Ascending='TRUE'
/></OrderBy></Query>">
• <SelectParameters>
• <asp:Parameter DefaultValue="ProjectEstimation" Name="ListName" />
• </SelectParameters>
• </SharePoint:SPDataSource>
• <asp:GridView ID="GridView1" runat="server" AllowPaging="true" AutoGenerateColumns="false"
• DataSourceID="ProjectEstimationList" EnableViewState="false">
• <Columns>
• <asp:BoundField DataField="TaskTitle" HeaderText="Name" />
• <asp:BoundField DataField="NoOfWeeks" HeaderText="Estimation" />
• </Columns>
• </asp:GridView>

13. Sandboxed Solution Overview
• You can deploy a solution directly onto your SharePoint Server
farm, or you can deploy the solution into a sandbox.
• You can deploy sandboxed solutions to quickly and more securely
solve business problems.
• Sandboxed solutions are like farm solutions except in the following
ways:
• they are rights-restricted and have a more permissive deployment policy than
farm solutions that enables programs to access only certain resources
• they are limited to the site collection to which they are deployed
• their server resource usage is monitored against an administrator-controlled
quota for the site collection.
• Solutions that you deploy into a sandbox, which are known as
sandboxed solutions, cannot use certain computer and network
resources, and cannot access content outside the site collection
they are deployed in.

14. Sandboxed Solution Overview
• The following list identifies the most common
things that an assembly that will run in a
sandbox cannot do:
• Connect to resources that are not located on the local
farm.
• Access a database.
• Change the threading model.
• Call unmanaged code.
• Write to disk.
• Access resources in a different site collection.

15. Farm Solution Deployment
• When a solution package is deployed to the
farm's solution store, it is called a 'farm
solution‘
• The components in a farm solution generally
run with full trust
• Only a farm administrator can install a farm
solution.

16. MJ Ferdous
ferdouscs@gmail.com
01715015093