SharePoint Development =================== Overview of SharePoint Development Development Tools for SharePoint 2010 Developer Dashboard in SharePoint Visual Studio 2010 templates for SharePoint

1. MJ Ferdous
SharePoint Architect
Founder, SharePoint Expert Community

3. SharePoint Development
– Overview of SharePoint Development
– Development Tools for SharePoint 2010
– Developer Dashboard in SharePoint
– Visual Studio 2010 templates for SharePoint

4. Overview of SharePoint Development
Check This Video (Presented by Paul Andrew,
Microsoft Corporation)
– http://msdn.microsoft.com/en-us/sharepoint/ee514561.aspx

6. Development Tools for SharePoint 2010
• Microsoft Visual Studio 2010: Visual Studio 2010 includes
14 project templates for SharePoint development. It also
includes visual Web Part and packaging designers, and
connects with Team Foundation Server for Application
Lifecycle Management (ALM).
• Microsoft SharePoint Designer 2010: With SharePoint
Designer 2010, you can configure SharePoint sites, create list
schema, add design elements, and build workflow models.
What’s more, SharePoint Designer and Visual Studio work
well together: You can use Visual Studio-based workflow
activities in SharePoint Designer, and you can export sites
from SharePoint Designer to Visual Studio.

7. Development Tools for SharePoint 2010
• Import Tool for Visual Studio 2010: Use this tool to
import a VSeWSS project that you created in Visual
Studio 2008 for SharePoint 2007 using the VSeWSS
extensions. The tool imports projects into Visual Studio
2010 and the resulting projects target SharePoint 2010.
The tool runs as a Visual Studio 2010 project template
and it is available here as source code and contains a
powershell script to build a VSIX file that can be directly
installed into Visual Studio 2010.
• URL: http://archive.msdn.microsoft.com/VSeWSSImport

8. Developer Dashboard in SharePoint
• The developer dashboard is a new feature in SharePoint
2010 that is design to provide additional performance
and tracing information that can be used to debug and
troubleshoot issues with page rendering time.
• The dashboard is turned off by default, but can be
enabled via the object model or stsadm (and PowerShell
too).
• When the dashboard is turned on you will find
information about the controls, queries and execution
time that occur as part of the page rendering process
• The information appears at the bottom of the page.

9. Here’s an example of what the “short” version of the output looks like :

10. Developer Dashboard in SharePoint
• As you can see, it provides information from the perspective of the event pipeline,
the web server and database.
• On the left side you can see the different events that fired in the page processing
pipeline and within that, you can see how long individual web parts took to within
those events.
• On the top right hand side you see information about the page processing as whole,
including the overall execution time, the amount of memory used in the processing
of the page request and the correlation ID, which can be of great value when trying
to link the page render to entries in the ULS log.
• Underneath the server information you will find a list of the different database calls
that were made through the object model by various components in the page itself
as well as the controls it hosts – all useful information.

11. Developer Dashboard in SharePoint
Use STSADM

12. Visual Studio 2010 templates for SP

13. Visual Studio 2010 templates for SP
Empty SharePoint Project
• The contents of an Empty SharePoint Project are common to all of the
project templates
Business Data Connectivity Model
• Business Data Connectivity Model projects let you integrate business data
into SharePoint. Business data can come from back-end server applications,
such as SQL Server, Siebel, and SAP.
• A Business Data Connectivity Model project is an Empty SharePoint Project
that contains a Business Data Connectivity Model item.
Content Type
• Content Type projects let you create custom content types based on an
existing (base) content type such as a document, announcement, or a task.
• The custom content type provides the same attributes and fields as the
base content type together with any fields you define.

14. Visual Studio 2010 templates for SP
Event Receiver
• Event receivers handle events for items in the SharePoint site, such as lists, Web
items, and workflows. The event receiver project template lets you handle
• The event receiver class can handle events that occur on the SharePoint site when
items such as files, fields, items, lists, attachments, Web sites, and workflows are
added, updated, deleted, or removed.
Import Reusable Workflow
• Import Reusable Workflow projects let you import a reusable, declarative workflow
created in SharePoint Designer 2010 into Visual Studio.
• The workflow exported from the SharePoint site as a .wsp file. Once imported into
Visual Studio, you can customize it, add code to it, and then deploy it to a
SharePoint site.
Import SharePoint Solution Package
• Import SharePoint Solution Package projects let you import an existing SharePoint
site, exported to a .wsp file, into Visual Studio.
• Once imported into Visual Studio, you can customize its item and redeploy them.

15. Visual Studio 2010 templates for SP
List Definition
• One of the major building blocks of a SharePoint site are lists, which are defined by list definitions. A
list definition is similar in concept to a base class or template — it defines all of the components of a
list, such as its fields, forms, views, and toolbar.
• This creates a standalone project that can contain other SharePoint project items such as content
types, list instances, and event receivers.
Module
• Modules (not to be confused with Visual Basic modules) contain any files that you want to
accompany the SharePoint project, such as development notes or a Readme file.
• The module project template creates an Empty SharePoint Project that contains a Module node.
• The Module node contains two project item templates: an XML definition file, which acts as a
manifest for the module, and a sample.txt file, a file included for example purposes.
Sequential Workflow
• A sequential workflow is a series of business logic steps, performed in sequence, until the last step is
completed.
• Sequential workflows are used to manage processes that involve SharePoint items such as lists and
documents
• You can create either site-level (global) workflows or list-level (local) workflows, and you can select
whether a workflow starts automatically or manually.

16. Visual Studio 2010 templates for SP
Site Definition
• Site definition projects contain everything that an Empty SharePoint Project
contains, plus
– A default .aspx page (used as the default Web page for the site.),
– An onet.xml file( which defines the components of the site), A
– webtemp xml file( which specifies the site definition configurations that appear in the Template
Selection section of the New SharePoint Site page)
State Machine Workflow
• A state machine workflow is a set of business logic states, transitions, and actions.
• The steps in a state machine workflow are not performed in sequence; instead, they
are triggered by actions and states.
• Like a sequential workflow, state machine workflows are associated with SharePoint
items such as lists and documents.
• Once again, you can create site-level (global) workflows or list-level (local)
workflows. You can also select whether a workflow starts automatically or manually.
Visual Web Part
• A visual Web part is a Web part that you create by using the Visual Web Developer
designer in Visual Studio.
• A Visual Web Part project is an Empty SharePoint Project that contains a Visual Web
Part item.