Share Point Development With Vs10
Download as PPTX, PDF0 likes510 views
This document provides an overview of the Visual Studio 2010 SharePoint Tools. It discusses how the tools provide an improved developer experience over prior versions, including features like SharePoint Explorer for site exploration, project templates, visual designers for common scenarios, and extensibility support. The tools aim to abstract away complexities for SharePoint developers by handling details like the RootFiles directory and building .wsp packages.
Share Point Development With Vs10
- 1. Visual Studio 2010 SharePoint Tools
- 2. OutlineIntroduction to VS2010 SharePoint ToolsSharePoint Tools Project StructureAdding SPIs to a ProjectSharePoint Tools Extensibility
- 3. SharePoint 2007 DevelopmentVisual Studio Experience Is LimitedVisual Studio Extensions for WSSVisual Studio Tools for Office with VS2008SharePoint developers reliant on community toolsDevelopers have to deal with tedious detailsManually editing CAML filesUnderstanding RootFiles directory of WSSManual edits to manifest.xml fileBuilding .wsp file for solution package
- 4. Visual Studio 2010 SharePoint ToolsEnd-to-end SharePoint 2010 developer storySharePoint Explorer for site explorationSharePoint 2010 project and item templatesVisual designers for core scenariosMigration path for Visual Studio 2008 for WSS 3.0Extensible by 3rd party developersBenefits to SharePoint developersAbstracts away details of RootFiles directoryAbstracts away details of building .wsp fileLessens/eliminates need for external utilities
- 5. SharePoint ExplorerAdd-in for Server Explorer windowEasy way to examine site artifactsQuick way to launch browser into siteSharePoint Explorer extensibilityDevelopers can write add-ins to populate nodes and provide contextual menu commands
- 7. OutlineIntroduction to VS2010 SharePoint ToolsSharePoint Tools Project StructureAdding SPIs to a ProjectSharePoint Tools Extensibility
- 8. SharePoint 2010 Project TemplatesSharePoint Projects have standard propertiesProject FileProject FolderActive Deployment ConfigurationInclude Assembly in PackageAssembly Deployment TargetSandboxed SolutionSite URLStartup Item
- 9. SharePoint 2010 Project StructureStandard Project NodesProperties(standard with all Visual Studio projects)References(standard with all Visual Studio projects)Features(added by SharePoint Tools)Package(added by SharePoint Tools)SharePoint Project Items(added using SharePoint Tools Project Item Templates)
- 10. Feature Node and Feature DesignerFeature node contains one or more featuresFeature designer provides design mode and XML text ModeCustomize feature properties in designer and/or property gridUse Context menu of Feature node to add feature event receiverFeature designer allows adding/removing SPIsCustomize feature activation dependencies
- 11. Mapped FoldersMapped Folders used to deploy to RootFilesLayouts folder maps to virtual path /_layoutsImages folder maps to virtual path /_layoutsYou can map other folders inside RootFiles directoryLayouts folder key to creating application pagesBest practice to create solution-specific folder inside Layouts
- 12. SPT Deployment OptionsTwo Deployment configuration by defaultDefaultNo Activation
- 13. The F5 Debugging ExperienceWhat does F5 do?Builds new version of .wsp fileDeactivates/uninstalls featureRetracts/deletes old .wsp fileAdds/deploys new .wsp fileActivates feature in target site (via Site Url)Attaches debugger to W3WP.EXE worker process (via Site URL)
- 14. Hello World with VS 2010 SharePoint Toolsdemo
- 15. OutlineIntroduction to VS2010 SharePoint ToolsSharePoint Tools Project StructureAdding SPIs to a ProjectSharePoint Tools Extensibility
- 16. 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, etcEach SPI has folder with SPI filesCompilation & deployment details abstracted away through SPI file properties
- 17. SPI File PropertiesProject tracks properties for each SPI FileVisual Studio properties for compilationSharePoint 2010 properties for deployment
- 18. SharePoint Project Item Templates
- 20. OutlineIntroduction to VS2010 SharePoint ToolsSharePoint Tools Project StructureAdding SPIs to a ProjectSharePoint Tools Extensibility
- 21. SharePoint 2010 Tools ExtensibilitySharePoint 2010 Project system extensibilityCustom extensions integrate into VS10 designer experienceUsed to create custom SPIs not supported out-of-boxMuch easier than standard VS extensibility modelSPI & Context Menu extensibilityExtend VS context menu for standard and custom SPIsProvide extensibility to enable access to SP server APISP Explorer Nodes & Menu extensibilityCreate extension to add a node to the SP ExplorerCreate extension to enhance existing node
- 22. Creating a Custom SPICreating a custom SPI TemplateCustom SPI is a creatable project item templateUsed to add SPI instance to SharePoint projectsYou can extend SPI with custom menus and properties Each SPI instance gets it own folder and can be initialized with a set of filesCustom SPI TemplateSPI can be extended with custom menu commandsCustom SPI Template used to add SPI instances to projectSPI can be extended with custom properties
- 23. CustomActiondemo
- 24. SummaryIntroduction to VS2010 SharePoint ToolsSharePoint Tools Project StructureAdding SPIs to a ProjectSharePoint Tools Extensibility
Editor's Notes
- #2: This lecture provides an introduction to the new SharePoint Tools that are included with Visual Studio 2010.
- #4: The developer experience for SharePoint 2007 has been less than ideal due to a lack of tool support, wizards and designers. Many developers coming from a background with .NET and ASP.NET development have been frustrated at the need to write batch files, work in the command line and write XML in a under-documented language know as Collaborative Application Markup Language (CAML).The functionality of Visual Studio Extensions for WSS 3.0 was much improved as it evolved from version 1.0 to 1.3. Although even the latest version does not provide an end-to-end solution for SharePoint development. Many SharePoint 2007 developers have an arsenal of community tools to accomplish many of the required tasks within SharePoint development.
- #5: The Visual Studio 2010 SharePoint Tools (SPT) represents a significant step forward for professional developers using SharePoint. SharePoint Explorer fallows quick exploration through a siteThis makes it possible to launch browser at specific place within siteSharePoint 2010 introduce a new project structure as well as project tmplates and project item templates. There are designers to create things like features and solution packages.One of the most appealing aspects of SPT is that it is extensibleYou can add your own custom project templates and item templatesYou can add menu commands into the Visual Studio UI.
- #6: The SharePoint Explorer is a simple easy-to-use tools.It provides a read-only treeview of a SharePoint site.Note that SharePoint Explorer only works on sites that are running locally
- #7: Simple on minute demo.Create a new team site in Central adminGo to Visual Studio and connect SharePoint Explorer to new siteShow what lists already exist within site.Click on list to bootstrap browser into site at list’s default view
- #20: Create an empty projectAdd VisualWebPart project itemAdd ApplicationPage project itemCreate mapped Images directory and add image