SHAREPOINT AND PROJECT CONFERENCE ADRIATICS ZAGREB, 11/28/2012

Visual Studio 2012PAUL J. SWIDER, REALACTIVITY

Objectives• Understand new requirements and

compatibility

• Understand changes for SharePoint developers

Agenda• Upgrade and Compatibility• New Features• Site Columns, Lists and Content Types• Visual Web Parts• Remote Development and Deployment• Profile and Testing

UPGRADE AND COMPATIBILITY

Compatibility with Previous Releases

• NET 4.5 is an in-place update of .NET 4 • Still using 3.5 for SharePoint 2010• SharePoint 2013 is now based on this .NET runtime version

v4.0.30319

• You can install and use Visual Studio 2012 alongside Visual Studio 2010

• Visual Studio Team Foundation Server 2012 requires 64-bit versions of server

Supported Upgrade Paths• Upgrade from .NET 4.5 Developer Preview to Beta

• Upgrade from .NET 4.5 Beta to Release (RTM)

• Upgrade from Visual Studio 11 Beta & .NET 4.5 Beta to Release Candidate

• Upgrade from Visual Studio 2012 Release Candidate to Release (RTM) (same edition only - e.g., Professional RC to Professional RTM)

• Upgrade from .NET 4.5 Release Candidate to Release (RTM)

Not Supported Upgrade Paths

• Upgrade from Visual Studio 11 Developer Preview to Beta

• Upgrade from Visual Studio 11 Beta to Release (RTM)

• Upgrade from Visual Studio 2012 Release Candidate to Release (RTM)

• Mismatched editions - e.g., Ultimate RC to Professional RTM

SharePoint Projects and SPI Assets• SharePoint Assets in Visual Studio (work items, source files,

tests and test results, builds, SharePoint Projects and SPI’s) will be carried forward when following supported upgrade paths.

• Backup and test projects first

SHAREPOINT SUPPORT

New SharePoint Specific Features• Create Lists and Content Types by Using New

Designers

New SharePoint Specific Features• Create Site Columns

• Create Silverlight Web Parts

• Publish SharePoint Solutions to Remote SharePoint Servers

• Test SharePoint Performance by Using Profiling Tools

New SharePoint Specific Features (Continued)

• Create Sandboxed Visual Web Parts

• Improved Support for Sandboxed Solutions.

• Support for JavaScript Debugging and IntelliSense for JavaScript

• Test Your Code by Using Microsoft Fakes Framework

FOR SHAREPOINT 2013

SharePoint 13 and Office 13• Two new project types• SharePoint Node• Office Node

• Client Web Part• Remote Event Receiver • UI Custom Action

• Determine Environment• Farm Solutions• Apps for SharePoint

• Farm Solutions• SharePoint 2013• Visual Studio 2012• Install Visual Studio Tools for Office• Not much new here

Setup Environment for SharePoint 2013

• SharePoint Online developer site, customized for creating and testing apps• Preconfigured for Apps

• "Napa" Office 365 Development Tools, to create your first apps right within the browser

• Office Professional Plus 2013 Preview• Exchange Online 2013 server

Create Office 365 Developer Site

• Develop apps for Office and SharePoint without having to install Visual Studio 2012

• Browser-based authoring tool • Napa vs. Visual Studio

Napa Office 365 Development Tools

Create apps for SharePoint 2013 Using OAuth

• Development of cloud-hosted apps for SharePoint• Automatically generate values for the client ID and the client secret

• Automatically generated for you when you’re debugging an app

Windows Azure Workflows in apps for SharePoint

• Model and automate business processes by creating Windows Azure workflows• Create custom activities for Windows Azure workflows

REMOTE DEVELOPMENT

Remotely Develop SharePoint Solutions• A server operating system and a version of SharePoint 2013 on

server.

• Developers must have Full Control permissions on the subsite of the server that's running SharePoint.• You currently can't debug remote event receivers or app event receivers in

Visual Studio

• Each developer’s system must also have the following components

installed on it.• Windows 7• Visual Studio 2012• SharePoint development tools in Visual Studio 2012

Accessing the Remote Server

• After you install the required components, you can access the remotely

• Specify the server name in the What SharePoint site do you want to use for debugging your App.

• Specify the server name in the Site Url property of an app for SharePoint project.

• When you run your app for SharePoint project, you are

prompted to log on to the remote server

• Deploy package files to the SharePoint server on your development computer for testing and debugging

• Publish a sandboxed SharePoint solution to a remote server.

Deploying and Publishing Packages

Deploy and Build Options

To upgrade successfully, a package must have a unique name

Deploy and Publish

demo

PROFILING SHAREPOINT

Profiling

Profiling - The process of observing and recording the performance behavior of your application as it runs.

• Bottlenecks• Inefficient code• Memory allocation issues

Profiling MethodsMethod Description

Sampling Collects statistical data about the work performed by an application.

Instrumentation Collects detailed timing information about each function call.

Concurrency Collects detailed information about multi-threaded applications.

.NET memoryCollects detailed information about .NET memory allocation and garbage collection.

Tier interactionCollects information about synchronous ADO.NET function calls to a SQLServer database.

Profile and Testing

demo

sponsors

DEMO TITLE

questions?

PLEASE ENTER YOUR BLOG URL

PLEASE ENTER YOUR TWITTER HANDLE

thank you.

SHAREPOINT AND PROJECT CONFERENCE ADRIATICS ZAGREB, 11/28/2012