Tools in Visual Studio 2010 for SharePoint 2010

Madhur AhujaAssociate Consultant, Microsoft ServicesEmail: madhur.ahuja@microsoft.com

Session Objectives and Takeaways

• Objective– Show the Visual Studio 2010 tools for building

SharePoint customizations

• Key Takeaways– Visual Studio 2010 offers a set of tools that

simplify SharePoint solution development

Development with SharePoint 2007

• Visual Studio Experience is limited– Visual Studio Extensions for WSS– Visual Studio Tools for Office with VS2008– SharePoint developers reliant on community tools.

• Developers have to deal with manual tasks– Manually editing CAML files– Understanding RootFiles directory of WSS– Manual edits to manifest.xml file.– Building .wsp file for solution package.

Visual Studio SharePoint Support

• Requires x64 operating system– Windows 7– Windows Vista SP1– Windows Server 2008– Windows Server 2008 R2

• SharePoint 2010 must be installed locally– SharePoint Foundation or SharePoint Server

• Visual Studio 2010

Visual Studio 2010 SharePoint Tools

• SharePoint 2010 developer story– SharePoint Explorer for site exploration– SharePoint 2010 project and item templates– Visual designers for core scenarios– Migration path for Visual Studio 2008 for WSS 3.0– Extensible by 3rd party developers– Reducing Complexity – XML Schemas, CAML, various config files– Improved F5 Experience– Improved Packaging & Deployment Experience

• Benefits– Abstracts away details of RootFiles directory– Abstracts away details of building .wsp file– Eliminates need for external utilities

SharePoint Explorer

• Add-in for Server Explorer Window– Easy way to examine site artifacts– Quick way to launch browser into site

• SharePoint Explorer extensibility– Developers can write add-ins to populate nodes

and provide contextual menu commands

SharePoint Explorer

Demo

SharePoint 2010 Project Template• SharePoint Projects have

standard properties– Project File– Project Folder– 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– Features (New)

– Package (New)

– SharePoint Project Items

Feature node and Feature Designer

• Feature node contains one or more features– Feature designer provides design mode– Customize feature properties in designer and / or

property grid– Feature designer allows adding/removing SPIs

Mapped Folders

• Mapped Folders used to deploy to RootFiles– Layouts folders maps to /_layouts– Images folder maps to /_layouts/Images– You can map other folders inside RootFiles directory.

• Layouts folder key to creating application pages– Best practice to create solution – specific folder inside

Layouts

Project Packaging

• Project packaging– Modify package properties with designer or XML

text– Designer allows you to add/remove feature and

SPIs

SPT Deployment Options

• Two Deployment Configuration by Default– Default– No Activation

The F5 Debugging Experience

• What does F5 do ?– Builds new version of .wsp file– Deactivates/Uninstalls features– Retracts/deletes old .wsp file– Adds/deploys new .wsp file– Activates Features in target site (via Site Url)– Attaches debugger to W3WP.EXE worker process

(via Site Url)

Creating Project using SharePoint Tools

Demo

Import SharePoint Solution(WSP)

• Wizard allows developer to select WSP• Modify imported items and Extend by adding

additional items, code, etc…

Import SPD Workflow

Demo

Questions/References

Visual Studio : http://blogs.msdn.com/visualstudio

Training Course on MSDN:http://channel9.msdn.com/learn/courses/SharePoint2010Developer/VisualStudio2010ToolsForSharePoint2010/

My Blog: http://blogs.msdn.com/mahujaEmail: madhur.ahuja@microsoft.comLinkedIn: http://in.linkedin.com/in/madhurahuja

Thanks to our sponsors