This document summarizes a presentation about new features in Visual Studio 2012 for developing SharePoint applications. It discusses upgrade paths, compatibility with previous versions, new project types for SharePoint 2013 and Office 2013, and tools for remote development and profiling SharePoint performance. New features include improved support for sandboxed solutions, JavaScript debugging, and the ability to publish solutions and deploy packages to remote SharePoint servers.

1. Visual Studio 2012
PAUL J. SWIDER, REALACTIVITY
SHAREPOINT AND PROJECT CONFERENCE ADRIATICS
ZAGREB, 11/28/2012

3. Objectives
• Understand new requirements and compatibility
• Understand changes for SharePoint developers

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

5. UPGRADE AND COMPATIBILITY

6. 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

7. 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)

8. 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

9. 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

10. SHAREPOINT SUPPORT

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

12. 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

13. 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

14. FOR SHAREPOINT 2013

15. SharePoint 13 and Office 13
• Two new project types
• SharePoint Node
• Office Node
• Client Web Part
• Remote Event Receiver
• UI Custom Action

16. Setup Environment for SharePoint 2013
• Determine Environment
• Farm Solutions
• Apps for SharePoint
• Farm Solutions
• SharePoint 2013
• Visual Studio 2012
• Install Visual Studio Tools for Office
• Not much new here

17. Create Office 365 Developer Site
• 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

18. Napa Office 365 Development Tools
• Develop apps for Office and SharePoint without having to install
Visual Studio 2012
• Browser-based authoring tool
• Napa vs. Visual Studio

19. 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

20. Windows Azure Workflows in apps for
SharePoint
• Model and automate business processes by creating Windows
Azure workflows
• Create custom activities for Windows Azure workflows

21. REMOTE DEVELOPMENT

22. 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

23. 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

24. Deploying and Publishing Packages
• Deploy package files to the SharePoint server on your
development computer for testing and debugging
• Publish a sandboxed SharePoint solution to a remote server.

25. Deploy and Build Options
To upgrade successfully,
a package must have a
unique name

27. PROFILING SHAREPOINT

28. Profiling
Profiling - The process of observing and
recording the performance behavior of your
application as it runs.
• Bottlenecks
• Inefficient code
• Memory allocation issues

29. Profiling Methods
Method 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 memory Collects detailed information about .NET memory allocation and garbage collection.
Tier interaction Collects information about synchronous ADO.NET function calls to a SQLServer database.

31. sponsors

33. DEMO TITLE

34. questions?
PLEASE ENTER YOUR BLOG URL
PLEASE ENTER YOUR TWITTER
HANDLE

35. thank you.
SHAREPOINT AND PROJECT CONFERENCE ADRIATICS
ZAGREB, 11/28/2012