Michael Mukalian: Building SharePoint 2010 Features and Solutions in Visual Studio 2010

Preview:

DESCRIPTION

Discussion and walkthrough of how to create SharePoint 2010 Features and Solutions with Visual Studio 2010

Citation preview

Building SharePoint 2010 Features and Solutions in

Visual Studio 2010

Saturday, July 31, 2010

Michael MukalianSharePoint Services MVP

Director, Architect, LiquidHub

Thank you sponsors!!

Remember to fill out your evaluations for your chance to win

cool prizes3 Apple IPAD 32 GB Wifi2 ASUS Netbooks

Also Some Books1 Typemock Isolator LicenseA 2-5 Day Course from SetFocus on SharePointTelerik RAD Controls Set1 DeliverPoint WFE 2010 license (Worth $1500)1 BCS Meta Man license (Worth $1200)1 Lightning Conductor 2010 WFE license (Worth $800)1 Lightning Storm Forums license. (Worth $600)

AgendaOverviewRequirements for DevelopmentElements of a SharePoint ProjectFeature NodeFeature DesignerPackage Node & DesignerPackaging ExplorerDemosReferences

Overview

With the introduction of Visual Studio 2010, Feature and Package (Solution) development are now integrated into the IDENew SharePoint 2010 Project Type & Item Templates assist in the creation of SharePoint assetsDesigners/Explorer facilitate examining the Feature & Package assets

Requirements For Development

Visual Studio ProfessionalSharePoint Foundation/Server64-bit Windows Server 2008/R2Vista SP1 & Windows 7Farm Administrator rights

Elements of a SharePoint Project

The project fileProject propertiesReferencesFeatures folderPackage folderKey file (strong-named key)

Feature Node

Contains one or more SharePoint project FeaturesA Feature is a ‘container’ for an additional function to SharePointDeployed to a specific scope

Farm, Web Application, Site (Collection), Web (site)

Project items added are also added to the feature nodeDouble-clicking the feature node displays the Feature Designer

Feature Designer

Creates FeaturesSets ScopesEstablish Feature DependenciesManually edit the Feature Manifest

Overriding the generated manifest will disable the Designer, and then all further changes will need to be done manually

Package Node and Designer

NodeGroups and view the hierarchical Package tree

DesignerGroups the SharePoint Items into a Solution Package

Packaging Explorer

Groups and view the hierarchical Package tree

Demo!

It’s peanut butter – demo time!

Bio

Michael Mukalian, SharePoint Services MVPEmails

michael@mukalian.commmukalian@liquidhub.com

Blog: The SharePoint Coffee Housewww.mukalian.com/blog

Twitter@mmukalian

Contributing AuthorMicrosoft SharePoint 2010 Administrator’s Pocket Consultant – Ben Curry

SharePoint Community in Philadelphia

• SharePoint (2010 & 2007)

• Administrators

• Developers

• IT Pros

• Architect Council after every meeting

• Meetings: Second Tuesday of the month, 6-9 PM

WEB: www.TriStateSharePoint.com

CONTACT: tss@mannsoftware.com

TWITTER: @tristateSP

Thanks!

Questions?

Recommended