SharePoint 2010 Development for ASP.NET Developers - SharePoint Saturday Houston 2011
Download as PPTX, PDF0 likes1,238 views
The document is an introduction to SharePoint Saturday Houston, providing logistical details and thanking sponsors. It includes technical requirements and guidance for SharePoint 2010 development for ASP.NET developers, highlighting tools and deployment strategies. Resources for further exploration of SharePoint development are also provided, along with contact information for the speaker, Corey Roth.
SharePoint 2010 Development for ASP.NET Developers - SharePoint Saturday Houston 2011
- 1. WelcomeSharePoint 2010 Development for ASP.NET Developers
- 2. Welcome to SharePoint Saturday HoustonThank you for being a part of the 2nd Annual SharePoint Saturday HoustonPlease turn off all electronic devices or set them to vibrate.If you must take a phone call, please do so in the hall so as not to disturb others.Thanks to our Platinum Sponsors:
- 3. InformationSpeaker presentation slides will be available at SharePointSaturday.org/Houston within a weekKeep checking website for future eventsThe Houston SharePoint User Group at www.h-spug.org, will be having it’s May meeting this Wednesday on May 11th. Please be sure to join us!Have a great day!
- 4. SharePoint 2010 Development for ASP.NET DevelopersCorey RothBlog: www.dotnetmafia.comTwitter: @coreyroth
- 5. Corey RothSharePoint Solutions Architect for StonebridgeMicrosoft SharePoint MVPSpecializing in ECM and SearchPassed all SharePoint 2010 certification examsMicrosoft Solutions AdvocateE-mail: [email protected]: @coreyrothBlog: www.dotnetmafia.comLaptop: Dell E6510 i5 2.4 GHz 8GBOracle VirtualBox 3.2.8 – 4GB on VM
- 6. What’s new?Visual Studio 2010!
- 7. 3-Minute Web Part DemoDemo
- 8. Getting StartedWhat do I need?
- 10. To Virtualize or not?
- 11. What else do I need?Windows Server 2008 R2 (or SP2) x64 / Windows 7 x64 for native installsSQL Server 2008 R2 (or SP1+CU2) x64 / SQL Server 2005 SP3 x64Virtualization Software (if virtualizing) – Oracle VirtualBox, VMWareWorkstation, Hyper-V, etc.Complete requirements at http://technet.microsoft.com/en-us/library/cc262485.aspx
- 12. SharePoint BasicsFarm (SPFarm) – Represents the collection of servers of the SharePoint deploymentWeb 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 togetherSite (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 buttonSolution (.wsp) – CAB file used for deployment
- 13. SharePoint Root Folder (aka 14 Hive)Location of most key SharePoint files: C:\Program Files\Common Files\microsoft shared\Web Server Extensions\14Called 12 in WSS3
- 14. Solution TypesFarm Solution – Same type of solution used in WSS3. No security restrictions unless using partial trustCan be deployed with Full Trust or Partial TrustSandboxed Solution – Deploys to the site collection with security limitationsCan only access a subset of the SharePoint object modelCannot elevate privilegesCan only access artifacts in the site collection it was activated onAdministrators can restrict the amount of resources availableIdeal for shared hosting environments / SharePoint Online
- 15. Visual Web PartA glorified ASP.NET User Control with a Web Part wrapperBuilt with a designerPreviously only available in Farm SolutionsSandbox compatible version available with Visual Studio 2010 SharePoint Power Tools
- 16. Visual Web Part DemoDemo
- 17. SharePoint APISPContext – Used to get reference to the current site or site collectionAll uses of SPSite or SPWeb must be disposed (use a using statement)Most collections do not have an “Exists” methodA few if them do now in SharePoint 2010Most objects require a call to .Update to save any changes madeSome API calls require elevated security – Pass a delegate to RunWithElevatedPrivleges
- 18. DemoDemo
- 19. DeploymentNo manual configuration or third party add-ons requiredVisual Studio builds features and solution package files for youVisual Studio deploys packages directly to SharePoint serverSolution packages can still be deployed to other servers via PowerShell
- 20. ResourcesHow to Build and Deploy a Web Part in SharePoint 2010http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2010/02/15/intro-to-sharepoint-2010-development-how-to-build-and-deploy-a-web-part.aspxHow to Build and Deploy a Web Part in WSS3http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2008/10/22/intro-to-sharepoint-development-how-to-build-and-deploy-a-web-part.aspx
- 21. Questions?Corey RothBlog: www.dotnetmafia.comTwitter: @coreyroth
- 22. Thanks to our Sponsors