270 likes | 533 Views
Visual Studio 2010 SharePoint Developer Tools Overview. Name Title Company. Agenda. Introduction to VS2010 SharePoint Tools SharePoint Tools Project Structure Adding SharePoint Project Items to a Project SharePoint Tools Extensibility. Improved VS2010 development expirience.
E N D
Visual Studio 2010 SharePoint Developer Tools Overview Name Title Company
Agenda • Introduction to VS2010 SharePoint Tools • SharePoint Tools Project Structure • Adding SharePoint Project Items to a Project • SharePoint Tools Extensibility
Improved VS2010 development expirience Introduction to VS2010 SharePoint Tools
SharePoint 2007 Development • Visual Studio Experience Is Limited • Visual Studio 2008 Extensions for WSS • SharePoint developers reliant on community tools • Developers have to deal with tedious details • Manually editing CAML files • Manual edits to manifest.xml file • Editing CAB DDF files for solution package • Understanding RootFiles directory of WSS • Attaching to the W3wp Process when debugging
Visual Studio 2010 SharePoint Developer Tools • End-to-end SharePoint 2010 developer story • SharePoint 2010 project and item templates • Visual designers for core scenarios • Migration Tool for VSeWSS Projects • SharePoint Explorer for site exploration • Extensible by 3rd party developers • Benefits to SharePoint developers • Abstracts away details of RootFiles directory • Abstracts away details of building solution files • Lessens/eliminates need for external utilities • Overall simplifies the development, deployment and debugging experience for developers
SharePoint 2010 Project Templates • All Projects built using standard structure • Common Project Properties • Active Deployment Configuration • Include Assembly in Package • Assembly Deployment Target • Sandboxed Solution • Site URL • Startup Item
SharePoint 2010 Project Structure • Standard Project Nodes • Properties • References • SharePoint 2010 Nodes • Features • Package • SharePoint Project Items (SPI) • Mapped Folders
Feature Node and Feature Designer • Feature node contains one or more features • Customize feature properties in designer and/or property grid • Use Context menu of Feature node to add feature event receiver and feature resource files • Feature designer allows adding/removing SPIs • Customize feature activation dependencies • Feature designer provides design mode and XML text Mode
Project Packaging • Project Packaging Designer • Modify package properties using property grid • Designer allows you to add/remove features and SPIs • Modify package properties with designer or XML
Mapped Folders • Mapped Folders used to deploy to SharePointRoot • Layouts folder maps to virtual path /_layouts • Images folder maps to virtual path /_layouts/images • You can map other folders inside SharePointRoot directory • Layouts folder key to creating application pages • Best practice to create solution-specific folder inside Layouts
SharePoint Project Template Deployment Options • Two Deployment configuration by default • Default • No Activation
The F5 Debugging Experience • What does F5 do? • Builds a new assembly • Packages project into .wsp file • Deactivates/uninstalls feature • Retracts/deletes old .wsp file • Performs IIS Reset • Adds/deploys new .wsp file • Activates feature in target site (via Site Url) • Attaches debugger to W3WP.EXE worker process (via Site URL)
SharePoint Explorer • Extends Server Explorer window • Easy way to examine site artifacts • Quick way to launch browser into site lists • Allows the Developer to stay in the VS IDE while having quick access to artifact properties • SharePoint Explorer extensibility • Developers can create extensions to add additional artifact nodes or add context commands to existing nodes
SharePoint Project Items (SPIs) • Projects built with SharePoint Items (SPIs) • SPI is a logical collection of project filesExamples of SPIs are WebParts, List Defs, Workflows, etc • Each SPI has folder with SPI files • Deployment details abstracted away through SPI file properties
SPI File Properties • Project tracks properties for each SPI File • SharePoint 2010 properties for deployment • Deployment Path & Deployment Type
Ignite WebParts demo
SharePoint 2010 Tools Extensibility • SharePoint 2010 Project system extensibility • Custom extensions integrate into VS2010 IDE • Used to create custom project and tool extensions • Much easier than standard VS extensibility model • SPI & Context Menu extensibility • Extend VS context menu for standard and custom SPIs • Provide extensibility to enable access to SP server API • SP Explorer Nodes & Menu extensibility • Create extension to add a node to the SP Explorer • Create extension to enhance existing node • SP Project extensibility • Create additional/custom deployment steps
SharePoint Extension Development VSIX Project Class Library VS 2010 x86 .Net 4.0 F5 VS 2010 x86 .Net 4.0 VSSPHost4 x64 .Net 3.5 SP1 SharePoint OM [Experimental Instance]
Summary • Introduction to VS2010 SharePoint Tools • SharePoint Tools Project Structure • Adding SharePoint Project Items to a Project • SharePoint Tools Extensibility
© 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.