600 likes | 828 Views
E N D
1. Olaf Feldkamp
Development Platform Advisor
Developer & Platform Group
Microsoft Schweiz GmbH
2. Agenda Part I: Development Environment
SharePoint 2010 Composite Solutions
Development Environment
Visual Studio 2010 SharePoint Tools
SharePoint Workflow
3. Microsoft SharePoint 2010 technologyThe Business Collaboration Platform for the Enterprise and the Web
4. SharePoint Composite Solutions Business Users – without Code
Use out-of-the-box features
Customize with SharePoint Designer and InfoPath
Application Developers – with Code
Web parts (ASP.NET 3.5, Silverlight), line-of-business data integration, list event receivers, workflows, workflow activities, application pages, content types, ..
Business Collaboration Applications
Operations – Reliability
Sandboxed solutions
Silverlight user interface (and business logic)
5. SharePoint 2010 Platform and Products
6. Ref. #1: Partner: EGELI Informatik AGCustomers: various
7. Reference #2: Partner: ADVIS AGCustomer: Kanton Luzern
8. Ref. #3: Partner: BPA Solutions SARLCustomers: various
9. Agenda Part I: Development Environment
SharePoint 2010 Composite Solutions
Development Environment
Visual Studio 2010 SharePoint Tools
SharePoint Workflow
10. Developer Investments in SharePoint 2010
11. SharePoint 2010Development Environment SharePoint Installation Options
Install on Windows Server 2008 SP2 x64 (or Windows Server 2008 R2 x64)
Use Microsoft Hyper-V and install on a virtual machine running a Windows Server 2008 SP2 x64 (or Windows Server 2008 R2 x64) guest operating system
Install on Windows 7 x64, Windows Vista SP1 x64, or Windows Vista SP2 x64
Use Microsoft Hyper-V and install on a virtual machine running a Windows 7 x64, Windows Vista SP1 x64, or Windows Vista SP2 x64 guest operating system
With Windows 7, you can create a VHD on which SharePoint is installed in Windows Hyper-V, and then configure Windows 7 with BDCEdit.exe so that it boots directly to the OS on the VHD
12. SharePoint 2010 Development Environment (2)
13. SharePoint 2010 Setup Hardware
X64-capable CPU, 4 cores, = 4 GB RAM
(= 8 GB for production use in a single server or multiple server farm)
Setting up the Development Environment for SharePoint (MSDN article)
Hardware and software requirements (TechNet article)
14. Agenda Part I: Development Environment
SharePoint 2010 Composite Solutions
Development Environment
Visual Studio 2010 SharePoint Tools
SharePoint Workflow
15. Visual Studio 2010 SharePoint Tools End-to-end SharePoint 2010 developer story
SharePoint Explorer for site exploration
SharePoint 2010 project and item templates
Visual designers for core scenarios
Extensible by 3rd party developers
Migration path for Visual Studio 2008 for WSS 3.0
Benefits to SharePoint developers
Abstracts away details of RootFiles directory
Abstracts away details of building .wsp file
Lessens/eliminates need for ext. utilities
16. The F5 Debugging Experience What does F5 do?
Builds new version of .wsp file
Deactivates/uninstalls feature
Retracts/deletes old .wsp file
Adds/deploys new .wsp file
Activates feature in target site (via Site Url)
Attaches debugger to W3WP.EXE worker process (via Site Url)
17. dEMO Visual Studio 2010 SharePoint Tools 17
18. Relational Lists: Joins Relational lists nowenforce referential integrity!
Lookup columns must be indexed (automatic)
Joins can be implemented using the API, CAML, or SharePoint Designer 2010
New properties on SPQuery
SPQuery.Join
SPQuery.ProjectedFields
19. LINQ to SharePoint Before SharePoint 2010: CAML was used for list queries
Used in SPQuery() and SPSiteDataQuery()
CAML must still be used for field and page rendering and schema definition
LINQ to SharePoint is similar to e.g. LINQ to Entities
Entity classes are strongly-typed, compile-time check
Intellisense helps query construction
New Assembly: Microsoft.SharePoint.Linq.dll
20. LINQ to SharePoint Create Entity Classes
Add this new output file to Visual Studio Project
Support for
List joins, join on lookup fields
Join multiple lists (A ? B ? C)
Project any field from joined list in a query without changes in list schema
21. dEMO LINQ to SharePoint
SharePoint Ribbon
22. CAML in Web Parts?New XsltListViewWebPart Replaces ListView-, ListForm-, DataViewWebPart
Web 2.0 View Framework
Data: replaces CAML for Views ? new Default: XSLT-based Views
CAML still used for Queries
List Schema
XSL
Easier edit in SharePoint Designer
Better User Interface
E.g. Inline editing
23. XsltListViewWebPart in Action
25. Architecture Explorer
26. demo Microsoft Test Manager 2010 26
27. Agenda Part I: Development Environment
SharePoint 2010 Composite Solutions
Development Environment
Visual Studio 2010 SharePoint Tools
SharePoint Workflow
28. Workflow in SharePoint 2010
29. Bringing SPD and Visual Studio together
30. Demo Workflow DevelopmentSharePoint Designer 2010 and Visual Studio 2010 Integration 30
31. Summary Build SharePoint Composite Solutions
Optionally, develop on Windows 7
Visual Studio 2010 provides a first class development experience for SharePoint
Use LINQ to SharePoint for queries
Improved workflow capabilities 31
32. Olaf Feldkamp
Development Platform Advisor
Developer & Platform Group
Microsoft Schweiz GmbH
33. Agenda Part II: Development Opportunities
Sandboxed Solutions
Service Applications
New APIs
REST API
Client Object Model
Business Connectivity Services
34. Custom Solutions with Office SharePoint Server 2007 Administrators can only secure solutions with Code Access Security
Hard to control what is being done in custom code
Custom code is biggest cause of SharePoint support cases
35. SharePoint 2010 Approach Sandboxed Solutions
Automatic triggers turn off custom solutions in a site collection that are too expensive on the server
36. The Sandbox A separate process where the solution runs
Exposes a subset of Microsoft.SharePoint
Code Access Security policy limits functionality
Site Collection Solution Gallery for deployment
Central Administration for managing and monitoring solutions
37. demo Developing and deploying a sandboxed solution 37
38. SharePoint Online Standard in 2010 will be a much larger subset of SharePoint Server 2010 Your Choice: On-Premises or Online
39. Agenda Part II: Development Opportunities
Sandboxed Solutions
Service Applications
New APIs
REST API
Client Object Model
Business Connectivity Services
40. SharePoint 2010 Service Applications SharePoint 2010 has a new, flexible, extensible and scalable services architecture, replacing SSPs
Simplified administration: Central Admin and PowerShell
Application isolation
1 service app uses 1 db, optionally, separate app pool
Extensible platform
Framework incorporated into SharePoint Foundation
WCF-based web services for communication
3rd parties can build and ship services
Lots of new in-box Services
SharePoint Server has nearly 20 services
Other products like Office Web Apps, Project Server, ship services
41. SharePoint
42. SharePoint 2010
43. SharePoint 2010
44. Deployment Scenario:Enterprise Resource Center
45. Agenda Part II: Development Opportunities
Sandboxed Solutions
Service Applications
New APIs
REST API
Client Object Model
Business Connectivity Services
46. Overview of SharePoint 2010 APIs
47. APIs: Functional Range Server Object Model
Complete API
Server code only
Web Services
More coverage in SharePoint 2010
Client Object Model
Very flexible
REST
Easiest to use
For fixed list schema
48. REST API Standards-based
JSON and Atom
CRUD operations on lists
…/_vti_bin/listdata.svc/Employees
Working with Visual Studio
Add Service Reference
http://server/yourSite/_vti_bin/listdata.svc
Based on latest WCF Data Services
3.5 SP1 projects need Data Services Update
.NET Framework 4 supported out-of-the box
49. demo REST API: SharePoint Foundation 2010 49
50. Client Object ModelEquivalent Objects All Client Object Models call client.svc (WCF Service)
Member names mostly the same from server to client
E.g.: SPWeb.QuickLaunchEnabled == Web.QuickLaunchEnabled
51. 1. ClientContext is the central object
2. Before you read a property, you have to ask for it
3. All requests must be committed in a batch
Getting started: 3 things to know loadQuery()loadQuery()
52. demo .NET Client Object model
Silverlight Client Object model 52
53. SharePoint 2010 APIsDecision Matrix
54. Agenda Part II: Development Opportunities
Sandboxed Solutions
Service Applications
New APIs
REST API
Client Object Model
Business Connectivity Services
55. Business Connectivity Services (BCS)
56. Development Approaches
57. demo Defining and deploying a BCS definition withSharePoint Designer 2010 57
58. BCS on- and offline in Outlook 2010
59. BCS Developmentwith Visual Studio 2010
60. Summary Sandboxed Solutions are the future
Write your own Service Applications
New REST and Client Object Model provide easy access to SharePoint for client-side code (e.g. Mashups)
Access to backend systems (read/write) with Business Connectivity Services 60