Your SlideShare is downloading. ×
  • Like
  • Save
Intro to SharePoint for Developers
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Intro to SharePoint for Developers


From devLInk 2010 in Nashville, TN.

From devLInk 2010 in Nashville, TN.

Published in Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads


Total Views
On SlideShare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide
  • In the beginning there was custom code. Every new project started out the same way.I am a firm believer in frameworksPlatform is a framework on steroids….we’ll talk about the Much Other Stuff
  • If it is just a 5-page brochure site with static text, SharePoint may not be for you.If it is simply a CMS solution for a public-facing web site, DNN may be a better toolSharepoint scalesSome people adopt it just because of the authentication integration with AD and security trimmingSome got it in the door through a requirement for a blogOthers just needed a simple workflow application over documents in a library
  • Compare to facebook apps, iGoogle gadgets, Vista gadgets
  • Key factor in user adoption and acceptance!
  • One partner said if his client won’t use SharePoint for a web project, he walks away…..that’s hard coreSame vocabulary
  • Collaboration – Blogs, wikis, discussions, check-in/check-out
  • Centralized knowledge managementTargetable to all levels of your organization
  • EAI - Popular at the turn of the millennium, but on the decline with the advent of SOAData is shared between the disparate systems…sometimes creating redundancy and latency….multiple versions of the truth…Which system is the system of record?
  • With SharePoint you get a service-oriented architecture and connectors via Business Connectivity ServicesYou end up with a single version of the truth and one portal to go to for all of your data mining
  • DV web part – put a plug for Vanessa’s sessionInfopath – story of SSG
  • Compare to BlackBerry, Windows Mobile or iPhoneCompare to facebook or twitter
  • Stats above from survey of 258 companies who are already using sharepointFrom 2008 SharePoint ReportAt the Microsoft-sponsored SharePoint Conference 2008, Bill Gates shared that Microsoft hadlicensed more than 100 Million seats to the platform and generated more than $US 1 Billionfrom that. To be sure, many of those seats fall under enterprise license agreements and may notreflect actual usage, but even if a fraction of those users actually logs into SharePoint each day,clearly it makes for the most significant – and fastest growing – information platform on themarket today.Number of seats is projected to grow by 25% each year.
  • Before frameworks and platforms, there was custom code. Every new project started out the same way.


  • 1. Introduction toSharePoint Development
    for .NET developers
  • 2. About me
    Rob Wilson – MCT, SharePoint MCTS/MCITP
    Gold Partner in Evansville, IN
    SharePoint 2003 20072010
    Twitter: @theRobManDotNet
  • 3. Agenda
  • 4. The SharePoint Platform
    SharePoint Foundation 2010 (f.k.a. WSS 3.0)
    SharePoint Server 2010 (f.k.a. MOSS 2007)
    Which edition is right for me?
    Why should I develop on a platform?
  • 5. Why Platforms?
    Significant cost reduction and standardization.
    10-15% of the effort. Lost projects because of one-time costs.
    Business Apps
    Much Other Stuff
    Custom Code
    MVC Framework
    SEO Friendly
    Business Apps
    Business Apps
    Separation of Roles
    Error Handling
    SEO Friendly
    Content Management
    Separation of Roles
    Administration Area
    Content Management
    Administration Area
    Error Handling
    Error Handling
    Menus (Menu Control)
  • 6. When the requirements call for it
    Not a brochure site
    Authentication and search required
    Does not have to be a large-scale project
    No-brainer for most intranets
  • 7. When you need self-service
    Web Parts (re-usability)
    Subscriptions and alerts
    Recycle Bin
    My Site
    Connecting with peers
  • 8. When you need personalization/socialization
    From a webmaster’s perspective
    Targeted content
    From a visitor’s perspective
    Ability to customize look and feel
    Tagging and newsfeeds
    Organizational chart and peer suggestions
  • 9. When you need workflow
    Based on Workflow Foundation
    In addition:
    SharePoint front-end
    Document libraries and task lists
    Workflow history lists
  • 10. When you want flexible development options
    Web Parts
    Object model
    Client object model (managed code, JavaScript, SilverLight)
    Web services
    Separation of development roles
    GUI expert, workflow developer, reports and queries, event handlers
    Varying levels of experience on a project team
  • 11. When you want focus on the business requirements
    Do not worry about how someone will find your application or how it integrates with the security model
    Eliminate the headache of external content repositories
  • 12. When you want consistency in your support footprint
    Common user interface
    Standardized code base
  • 13. When you want to take advantage of the inherent features of the platform
    Content Management
    Business Intelligence
    Forms and Business Processes
  • 14. When you want to offset the cost of development
    More time spent in the planning and design stages should surface more out-of-the-box features [that should save time later]
    Out-of-the-box features should reduce the cost of custom software development
    Developer focus should shift immediately to the business needs and extending the out-of-the-box features
  • 15. When you need SOA
    Rest API expose SharePoint content
    Use the object model to create your own web services/WCFs
  • 16. When you need composite applications
    Dashboards, Mash-ups
    Business Connectivity Services
    All levels of your organization
  • 17. When you need composite applications
    Before SharePoint
    Legacy Systems
  • 18. When you need composite applications
    Legacy Systems
  • 19. When you need Single Sign On
    Multiple built-in authentication options
    Support for third-party authentication providers
    Built-in SSO provider
    Manages credentials for other apps on your intranet
  • 20. When you need off-line support of your data
    Office Integration
    Importing/exporting lists from/to excel
    Linked tables with Access
    Calendar/Task List integration with Outlook
    Groove/SharePoint Workspace
  • 21. When you need auditing and retention policies
    Log just the events you need for what lists are of interest to you
    Develop auditing reports using SSRS
    Develop/customize workflows for content retention and disposal
  • 22. When you need to equip your power users
    SharePoint Designer
    Custom queries with Data View Web Part
    Simple workflows
    Simple forms – really!
  • 23. When your culture allows for it
    User acceptance is key
    Large implementations are going to take a team of both IT and line of business users
    Will likely require a paradigm shift (point is to share, not hoard)
    Small, quick wins where possible
  • 24. When a development community is important to you
    Blogs and forums
    Community video tutorials
    User Groups
    Commercial/Open Source Features and Web Parts
  • 25. When you can no longer resist
    Up to 92% satisfaction rating in the categories of functionality, end user experience, total cost of ownership and end user acceptance
    Up to 59% of all companies are projected to have SharePoint or an equivalent platform by the end of this 2008 and that number was projected to increase 19% between 2009 and 2011
  • 26. When you want to build your resume 2,800 jobs (JUL 2010) 1,000+ jobs (JUL 2010) ~500 jobs (JUL 2010)
  • 27. Alternatives
    Free Bulletin
    Free Blog Host
    JavaScript Menu Builder
    Embedded Google Calendar
    Spam-friendly form submission scripts
    Coffee Cup Editor for CMS
  • 28.
  • 29. Overview of SharePoint Development Tools
    InfoPath 2010
  • 30. SharePoint Development Environment for .NET
    SharePoint no longer required on development machine in some cases, but recommended
    Virtual environment
    64-bit is a must
    RAM is your friend
    Upcoming session at devLINK
  • 31. Visual Studio Solutions for SharePoint
    Formerly 2
    Gaps filled with CodePlex add-ons
    Now 14 OOB
  • 32. SharePoint Solution Architectures
    * New Client Object Model exists for Managed .NET, Silverlight and ECMA Script
  • 33. Object Model – Server Architecture
  • 34. SPSite
    Object Model – Site Architecture
  • 35. Feature Activated
    List Definition with Event Handler
  • 36.
  • 37. Client Object Model
  • 38. Client Object Model Files
    Managed Client (CLR based)
    C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions14ISAPI
    Microsoft.SharePoint.Client (281 kb)
    Microsoft.SharePoint.Client.Runtime (145 kb)
    FYI: Microsoft.SharePoint.dll is 15.3 mb
    JavaScript Client
    C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions14TemplateLayouts
    SP.js (380 kb)
    SP.Core.js (13 kb)
    SP.Runtime.js (68 kb)
  • 39. Client Object Model Files
    Silverlight Client
    C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions14TemplateLayoutsClientBin
    Microsoft.SharePoint.Client.Silverlight (262 kb)
    Microsoft.SharePoint.Client.Silverlight.Runtime (138 kb)
  • 40. Client Object Model
    Allows you to write SharePoint applications that run on different platforms w/o using web services
    Traditional .NET, Web/JavaScript and Silverlight developers can use familiar syntax
  • 41. New Features
    Ease of deployment
    Publish and run if SharePoint on local host
    Package and deploy if SharePoint remote
    Step through code if SharePoint on local host
    Sandbox solutions
    Allow applications to be deployed at the site collection level by a site collection administrator (as opposed to farm-level equivalent)
  • 42. New Features
    Silverlight Web Part
    Upload XAP file to a document library and reference it
  • 43. New Features
    LINQ Support
    No longer restricted to just CAML queriesif writing server-based code
    Create strongly typed SharePoint objects using SPMetal utility
  • 44. New Features
    Dialog framework
    External Lists
    Looks and behaves like a SharePoint list
    Stored in SQL Server or some other data source
  • 45. For More Information
    Hands On Labs:
    Or (you’re welcome!)
    Developer Training Kit
    MSDN Training Videos