From devLInk 2010 in Nashville, TN.

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 Email: rwilson@KellerSchroeder.com Twitter: @theRobManDotNet Blog(s): http://sharepointblog.kellerschroeder.com http://www.therobman.net/blog

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? Platform Significant cost reduction and standardization. 10-15% of the effort. Lost projects because of one-time costs. Business Apps Much Other Stuff RAD Custom Code MVC Framework SEO Friendly Business Apps Business Apps Standards-Based Search RAD Separation of Roles Error Handling SEO Friendly Uniformity Standards-Based Search Content Management Separation of Roles Administration Area Content Management Administration Area Uniformity Error Handling Error Handling Menus Menus Menus (Menu Control) Authorization Authorization Authorization Authentication Authentication Authentication

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 RSS Recycle Bin My Site Connecting with peers Publishing

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 Vocabulary Standardized code base

13. When you want to take advantage of the inherent features of the platform Collaboration Portal Content Management Search 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 ERP Before SharePoint CRM Legacy Systems Middleware

18. When you need composite applications ERP SharePoint CRM 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 InfoPath 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 CodePlex 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 Dice.com: 2,800 jobs (JUL 2010) Monster.com: 1,000+ jobs (JUL 2010) HotJobs.com: ~500 jobs (JUL 2010)

27. Alternatives Free Bulletin Board Free Blog Host JavaScript Menu Builder Embedded Google Calendar Spam-friendly form submission scripts Coffee Cup Editor for CMS

28. http://www.tinyurl.com/sp2010editions Editions

29. Overview of SharePoint Development Tools InfoPath 2010 smtp4dev

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 SPWeb SPList SPField SPItem Object Model – Site Architecture

35. Feature Activated List Definition with Event Handler Demo

37. Client Object Model Demo

38. Client Object Model Files Managed Client (CLR based) C:rogram Filesommon Filesicrosoft Sharedeb Server Extensions4SAPI Microsoft.SharePoint.Client (281 kb) Microsoft.SharePoint.Client.Runtime (145 kb) FYI: Microsoft.SharePoint.dll is 15.3 mb JavaScript Client C:rogram Filesommon Filesicrosoft Sharedeb Server Extensions4emplateayouts SP.js (380 kb) SP.Core.js (13 kb) SP.Runtime.js (68 kb)

39. Client Object Model Files Silverlight Client C:rogram Filesommon Filesicrosoft Sharedeb Server Extensions4emplateayoutslientBin 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 Debugging 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: http://www.microsoft.com/downloads/details.aspx?FamilyID=c010fc68-b47f-4db6-b8a8-ad4ba33a35c5&displaylang=en Or http://bit.ly/sp2010hol (you’re welcome!) Developer Training Kit http://bit.ly/sp2010devkit MSDN Training Videos http://www.mssharepointdeveloper.com