What’s New in SharePoint 2010 SharePoint 2010 Development Primer New Developer Tools for SharePoint 2010 SharePoint 2010 Integration with PowerShell

Windows SharePoint Services (WSS v3) Site and Workspace Provisioning Engine Out-of-the-box Collaboration Services Microsoft Office SharePoint Server (MOSS) User Profiles, Search, Workflows, WCM BDC, Excel Services, Forms Services, ECM Windows SharePoint Services 3.0 (WSS v3) Browser Clients MS Word Clients MS Outlook Clients Microsoft Office SharePoint Server 2007 (MOSS) Windows Server 2003 or 2008 (32-bit or x64) Internet Information Services 6.0 or 7.0.NET Framework 3.0

An evolved version of MOSS and WSS v3 Microsoft SharePoint Server 2010 Microsoft SharePoint Foundation 2010 Development can now be done on client OS Significant enhancement for many development teams Microsoft SharePoint Foundation 2010 Browser Clients MS Word Clients MS Outlook Clients Microsoft SharePoint Server 2010 Windows Server 2008 (x64 only) for Production Environments Windows 7 or Vista (x64 only) for Development Environments only Internet Information Services 7.0.NET Framework and ASP.NET 3.5 SP1

Connect and Empower People Cut Costs with a Unified Infrastructure Rapidly Respond to Business Needs Communities Search Sites Composites ContentInsights

Improvements to UI and accessibility features Better Tools for Developers and Designers End-to-end Integration with PowerShell Improvements to lists and events New WSS integration with LINQ New client-side object model and runtime Enhanced support for developing workflow applications New Extensible architecture for service applications Evolving story for integrating SharePoint with external data New Connector framework enhances Search architecture User Solutions and Partially Trusted Code The shift to claims-based security

Server ribbon In-place editing Popup dialog AJAX refresh

What’s New in SharePoint 2010 SharePoint 2010 Development Primer New Developer Tools for SharePoint 2010 SharePoint 2010 Integration with PowerShell

- Farm (SPFarm) - Web Application (SPWebApplication) - Site Collection (SPSite) - Site (SPWeb) - List (SPList) - Item (SPListItem) - Document Library (SPDocumentLibrary) - File (SPFile) - Folder (SPFolder)

Make sure that your start VS 2010 as Admin Required for attaching VS 2010 debugger to IIS Worker Process (W3WP.EXE)

What’s New in SharePoint 2010 SharePoint 2010 Development Primer New Developer Tools for SharePoint 2010 SharePoint 2010 Integration with PowerShell

SharePoint 2010 development brings new tools Created by group within Visual Studio 2010 team Major step forward from SharePoint 2007 development New tools target SharePoint 2010 only These new tools are introduced in lecture 2 SharePoint ExplorerNew Project and Item Templates New Project Structure

SPD shell’s focus on SharePoint objects SPD objects have relationships Intuitive navigation between SPD objects SPD work migrates to Visual Studio 2010 SPD customization work exported to.wsp files.wsp files imported into Visual Studio SPD 2007 UI SPD 2010 UI New UI focused on SP Objects

What’s New in SharePoint 2010 SharePoint 2010 Development Primer New Developer Tools for SharePoint 2010 SharePoint 2010 Integration with PowerShell

Previous version of WSS relies on STSADM.EXE Used for command line administration and scripting SharePoint 2010 adds support for PowerShell PowerShell support effectively replaces STSADM.EXE SharePoint admins/devs must learn PowerShell basics You can write powerful scripts against WSS OM You can develop custom PowerShell snap-ins STSADM.EXE We’ll miss you old friend

What is PowerShell? A modern replacement for the CMD (command) shell A powerful scripting environment for administration Note – VM for this course uses PowerShell V2 (CTP3) PowerShell fundamentals Cmdlets (e.g. Get-Process and Stop-Process) Pipelining and formatting features Provider-based model for accessing resources

(4) Redirect output to new text file (2) Filter results using where clause (1) Execute a Cmdlet (3) Add formatting instructions

You can author PowerShell scripts Scripts have.ps1 extension Local execution policy must be configured Scripts will not execute under default execution policy of restricted Scripts can execute under execution policy of unrestricted. Scripts that are not signed result in prompting user for permission to execute. Scripts can execute under execution policy of bypass. This mode suppresses prompting user for permission to execute.

Supports Color-coding, IntelliSense and debugging

Explicitly load SharePoint PowerShell snap-in from console or script Implicitly load snap-in by using link in Windows Start menu Begin using SharePoint Cmdlets

PowerShell was created with extensibility in mind SharePoint developers can create custom snap-ins STSADM extensions now considered deprecated

What’s New in SharePoint 2010 SharePoint 2010 Development Primer New Developer Tools for SharePoint 2010 SharePoint 2010 Integration with PowerShell