2. We are not ‘Chaks’ !Chak’s had to withdraw due to illness. We are the reinforcements… Nick Hadlee – Intergen nicholas.hadlee@intergen.co.nz http://hadlee.net.nz @nickhadlee Chan (MVP) – Knowledge Cue chan@knowledgecue.co.nz http://www.chandima.net/Blog @chandimak Who are we?
3. SharePoint Architecture Fundamentals Introduction to SharePoint Development SharePoint Object Model Overview Building customisations without code SharePoint Development Best Practices Feature and Solution Overview Deploying site artefacts using features What we’ll cover…
4. What is SharePoint? High-level Architecture The Farm Web Applications Service Applications Administration Containers Site Collections Sites Lists Items Introduction to SharePoint
5. WFE – Some changes, mostly optimization App Server – Many changes SQL – Some changes, heavy optimization Sum total is: Architecture is familiar, but there are many more design choices now 2010 is far more flexible than 2007 (yet complex) SP2010 Architectural Components Web Tier Application Tier SQL Tier
7. No longer a separate SSP web site SA’s managed via central admin Pick and choose your service apps (SA) If you don’t need a service app, don’t add it Web apps can consume SAs on an individual basis Each web app can use any combination of all available SA’s Deploy multiple instances of the same SA Just give each one a unique name Reuse SA instances across multiple web apps in farm Service Applications vs SSP
8. Access Services Business Data Catalog Excel Services Managed Metadata Service People Search Service Application Secure Store Service State Service Usage and Health data collection Visio Graphics Service Web Analytics Service Application Word Conversion Service Application Services – “a la carte” Search User Profiles Excel Calc BDC Visio WAC 3rd party Service http://itweb/ http://hrweb/
9.
10. How do we talk to SharePoint? Server and client object models The SharePoint API PowerShell Web Services SharePoint Object Model Overview
11. Client Object Model - You don’t have to run on the server any more… SharePoint Object Model Overview
13. Building customisations without code (VS) using SharePoint Designer and other techniques Lists and views List view web part Connected web parts (e.g. Filters) Content query and roll up Data View Web Part (DVWP) Info Path Form Web Part Building CustomisationsWithout Code
14. The developer stack – where does my stuff go? The 14 hive {SharePoint Root} The Web root {IIS} The GAC and the BIN Content Databases SharePoint Development Overview
15. SharePoint Development Best Practices – general guidelines to adhere to when customising SharePoint Use solutions (WSP) and features Object disposal – SharePoint objects are resource hungry Performance considerations - caching Don’t touch the 14 hive {SharePoint Root} Don’t modify the web.configfiles Don’t modify the OOTB SharePoint files manually Don’t deploy manually to the GAC Don’t directly access the SharePoint databases Reference: Common Coding Issues When Using the SharePoint Object Modelmsdn.microsoft.com/en-us/library/bb687949(office.12).aspx SharePoint Development Best Practices
17. Feature and Solution Overview – Best practices for deploying customisations to SharePoint Features and Deployment – How do features and solutions work? Feature Scopes Farm Web Application Site Collection Site Feature and Solution Overview
18. SharePoint is natively supported with Visual Studio 2010 template solutions Developing with Visual Studio 2010
19. The ASP.NET way of thinking vs. SharePoint way of thinking Databases vs. Lists Where does/should the data live? DataGrids and Repeaters, vs. Views, Web Parts and Forms Leveraging the SharePoint platform You can still develop anything in SharePoint (its on top of .NET) but do you need to? Build vs. Buy The Balancing Act Development, Maintenance and Deployment Service Packs and Versions 95% - do you need that extra 5%? Development Scenarios
20. Business Connectivity Services Web parts and Custom Development Business Intelligence Web Services InfoPath Workflow Enterprise Integration
22. Workflow – OOTB, Visio, SharePoint Designer, Visual Studio Workflow
23. SharePoint List Forms – OOTB SharePoint List Forms – SharePoint Designer SharePoint List Forms – InfoPath InfoPath Form Libraries Reference: Comparing SharePoint List and Form Library Formsblogs.msdn.com/b/infopath/archive/2010/04/22/comparing-list-and-form-library-forms.aspx Forms Use a list form if you just need to collect data and store it on SharePoint. Use a form library form if you want more advanced functionality such as complex or repeating data or code.
25. SharePoint User Groups – www.dot.net.nz SharePoint Developer Centremsdn.microsoft.com/en-us/sharepoint SharePoint 2010 SDKmsdn.microsoft.com/en-us/library/ee557253.aspx Channel 9channel9.msdn.com/learn/courses/SharePoint2010Developer Patterns and Practicesspg.codeplex.com General Developer Guidancewww.rharbridge.com/?page_id=259 SharePoint on TechNettechnet.microsoft.com/en-us/sharepoint Useful Resources
26. MSDN SharePoint Forumssocial.msdn.microsoft.com/Forums/en/category/sharepoint SharePoint Overflowwww.sharepointoverflow.com SharePoint DevWikiwww.sharepointdevwiki.com SharePoint Team Blogblogs.msdn.com/b/sharepoint SharePoint Developer on Microsoft.comwww.microsoft.com/click/sharepointdeveloper Community Forums and Helpful Sites
27. Wellington – New Zealand – 16th17th March Technical Business Voice of the Customer “GettothePoint” pre and post conference training www.sharepointconference.co.nz SharePoint Conference 2011
28. PowerShell to STSADM Mapping http://technet.microsoft.com/en-us/library/ff621084.aspx Best Practices: Using Disposable Windows SharePoint Services Objects http://msdn.microsoft.com/en-us/library/aa973248(office.12).aspx More Links
The main objective of the slide is to draw the attention to the three tiers. Today the objective is that you will know more about the SQL tier and how to plan for that.
Planning and architecture for SharePoint Server 2010technet.microsoft.com/en-us/library/cc261834.aspx
Service Applications – What these are and why they are used.Service Applications are the most significant change in SP2010. Basically means that you can turn on and use specific functionality for various scenarios.However the architectural planning is now significantly complex.