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

1. SharePoint 2010 Development for ASP.NET Developers Corey Roth Blog: www.dotnetmafia.com 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 E-mail: coreyroth@gmail.com Twitter: @coreyroth Blog: www.dotnetmafia.com

3. What’s new? Visual Studio 2010!

4. 2-Miunute Web Part Demo Demo

5. Getting Started What do I need?

6. You need… RAM!

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 http://technet.microsoft.com/en-us/library/cc262485.aspx

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:rogram Filesommon Filesicrosoft sharedeb Server Extensions4 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 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 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 http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2010/02/15/intro-to-sharepoint-2010-development-how-to-build-and-deploy-a-web-part.aspx How to Build and Deploy a Web Part in WSS3 http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2008/10/22/intro-to-sharepoint-development-how-to-build-and-deploy-a-web-part.aspx

18. Questions? Corey Roth Blog: www.dotnetmafia.com Twitter: @coreyroth