Your SlideShare is downloading. ×
SharePoint 2010 Development for ASP.NET Developers  -  SharePoint Saturday Ozarks 2010
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

SharePoint 2010 Development for ASP.NET Developers - SharePoint Saturday Ozarks 2010


Published on

Slides from my SharePoint 2010 Development talk at SharePoint Saturday Ozarks.

Slides from my SharePoint 2010 Development talk at SharePoint Saturday Ozarks.

Published in: Technology

1 Like
  • 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
  • Demo building and deploying a web part in under two minutes.
  • Demo the Visual Web Part
  • Demo how to set up managed properties.
  • Updated the Visual Web Part to make some API calls.Demo Features and Solution editor in Visual StudioShow other SPIs
  • Demo how to set up managed properties.
  • Transcript

    • 1. SharePoint 2010 Development for ASP.NET Developers
      Corey Roth
      Twitter: @coreyroth
    • 2. Corey Roth
      Consultant for Stonebridge
      Worked in Consumer Electronics, Travel, Advertising, and Energy industries
      Currently doing SharePoint development specializing in Enterprise Search
      Microsoft Award for Customer Excellence (ACE) Winner
      MCTS: MOSS 2007 Configuring, Developer
      Twitter: @coreyroth
    • 3. What’s new?
      Visual Studio 2010!
    • 4. 2-Miunute Web Part Demo
    • 5. Getting Started
      What do I need?
    • 6. You need…
    • 7. To Virtualize or not?
    • 8. What else do I need?
      Windows Server 2008 R2 (or SP2) x64 / Windows 7 x64 for native installs
      SQL Server 2008 R2 (or SP1+CU2) x64 / SQL Server 2005 SP3 x64
      Virtualization Software (if virtualizing) – Sun VirtualBox, VMWareWorkstation, Hyper-V, etc.
      Complete requirements at
    • 9. SharePoint Basics
      Farm (SPFarm) – Represents the collection of servers of the SharePoint deployment
      Web Applications (SPWebApplication) – Typically one or more of these maps to a web site in IIS (i.e.: Port 80)
      Site Collection (SPSite) – Will have at least one. Groups sites together
      Site (SPWeb) – Represents a site or subsite in a Site Collection. Contains pages, lists, etc.
      Feature – Allows code and SharePoint changes to occur at the click of a button
      Solution (.wsp) – CAB file used for deployment
    • 10. SharePoint Root Folder (aka 14 Hive)
      Location of most key SharePoint files: C:Program FilesCommon Filesmicrosoft sharedWeb Server Extensions14
      Called 12 in WSS3
    • 11. Solution Types
      Farm Solution – Same type of solution used in WSS3. No security restrictions unless using partial trust
      Can be deployed with Full Trust or Partial Trust
      Sandboxed Solution – Deploys to the site collection with security limitations by a site collection admin
      Cannot elevate privileges
      Can only access artifacts in the site collection it was activated on
      Administrators can restrict the amount of resources available
      Ideal for shared hosting environments / cloud
      Solutions run in their own process (SPUCWorkerProcess.exe)
    • 12. Visual Web Part
      A glorified ASP.NET User Control with a Web Part wrapper
      Built with a designer
      Only available in Farm Solutions (third party options available for Sandboxed)
    • 13. Visual Web Part Demo
    • 14. SharePoint API
      SPContext – Used to get reference to the current site or site collection
      All uses of SPSite or SPWeb must be disposed (use a using statement)
      Most collections do not have an “Exists” method
      A few if them do now in SharePoint 2010
      Most objects require a call to .Update to save any changes made
      Some API calls require elevated security – Pass a delegate to RunWithElevatedPrivleges
    • 15. Demo
    • 16. Deployment
      No manual configuration or third party add-ons required
      Visual Studio builds features and solution package files for you
      Visual Studio deploys packages directly to SharePoint server
      Solution packages can still be deployed to other servers via PowerShell
    • 17. Resources
      How to Build and Deploy a Web Part in SharePoint 2010
      How to Build and Deploy a Web Part in WSS3
    • 18. Questions?
      Corey Roth
      Twitter: @coreyroth