• Save
SharePoint Development (Lesson 3)
Upcoming SlideShare
Loading in...5
×
 

SharePoint Development (Lesson 3)

on

  • 635 views

SharePoint Development ...

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

Statistics

Views

Total Views
635
Views on SlideShare
635
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Demo on Content Editor, Page Viewer Web Part
  • Customizing List views (Conditional formatting)

SharePoint Development (Lesson 3) SharePoint Development (Lesson 3) Presentation Transcript

  • MJ FerdousSharePoint ArchitectFounder, SharePoint Expert Community
  • 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
  • What are WebParts?
  • WebParts through browser
  • DEMOWorking withWebParts through browser
  • WebPart through SP Designer Customizing List View (Conditional Formatting)
  • DEMOCustomizing WebPart through Designer Customizing List views (Conditional formatting)
  • 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
  • DEMOBuild a custom web part using vs2010 and deploy at SharePoint site
  • DEMOCreate a Visual web part
  • 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>
  • 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.
  • 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.
  • Farm Solution Deployment• When a solution package is deployed to the farms 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.
  • MJ Ferdousferdouscs@gmail.com01715015093