Please respect.

My First Presentation for SharePoint Dev

New in SharePoint Development

• Create lists and content types by using designers.
  You can more easily create a list or a content type by using a designer to set up and lay out the contents of the list or content type. For more information, see Creating Site Columns, Content Types, and Lists for SharePoint.
• Create site columns for SharePoint sites.
  You can more easily create SharePoint site columns, which are also known as "fields," by using an item template. For more information, see Creating Site Columns, Content Types, and Lists for SharePoint.
• Add Silverlight web parts to your SharePoint projects.
  You can more easily and conveniently create Silverlight web parts by using a project template. For more information, see Walkthrough: Creating a Silverlight Web Part that Displays OData for SharePoint.
• Publish SharePoint solutions to remote SharePoint sites.
  You can publish SharePoint solutions to remote SharePoint sites, in addition to local SharePoint sites. For more information, see Deploying, Publishing, and Upgrading SharePoint Solution Packages.
• Increase SharePoint performance by using profiling tools.
  By using tools in Visual Studio, you can identify code and other elements that are slowing down your SharePoint projects and perform other performance profiling. For more information, see Profiling the Performance of SharePoint Applications and Analyzing Application Performance by Using Profiling Tools.
• Create sandboxed visual web parts..
  You can include visual web parts in sandboxed SharePoint projects, not just farm projects.
• Create sandboxed solutions more easily.
  When you’re working on a sandboxed solution in Visual Studio, only compatible APIs appear in Intellisense, and a compiler error occurs if you try to use farm-only API calls.
• Debug JavaScript more easily.
  You can debug JavaScript in SharePoint projects, and IntelliSense is provided when you're coding JavaScript in SharePoint projects. URLs for JavaScript are resolved for visual web parts in sandboxed solutions.
• Develop SharePoint projects more easily by using streamlined project templates.
  To help streamline SharePoint development, some SharePoint project templates from the previous version of Visual Studio were moved into project item templates. For a full list and descriptions of the project and project-item templates, see SharePoint Project and Project Item Templates.
• Test your code by using the Microsoft Fakes framework.
  SharePoint projects support Microsoft Fakes, which is an isolation framework in which you can create delegate-based test stubs and shims in .NET Framework applications and test your code by isolating your unit tests from the environment. For more information, see Verifying and Debugging SharePoint Code by Using ALM Features.

Office Development

• Create apps for Office.
  An app for Office is a type of Office solution that provides new experiences within Office applications by surfacing web technologies and cloud services within Office documents, email messages, meeting requests, and appointments. For more information, see Create Apps for Office by using Visual Studio.
• Develop Solutions for Microsoft Office 2013 Preview.
  By using Microsoft Office developer tools, you can create document-level customizations and application-level add-ins for Office 2013 Preview applications. To obtain project templates for Office 2013 Preview applications, you download and install the Microsoft Office Developer Tools for Visual Studio 2012.
  
  
  Reference : http://msdn.microsoft.com/library/vstudio/bb386063.aspx

MORE VS 2012 VIDEOS CHECK HERE

http://channel9.msdn.com/Series/Visual-Studio-2012-Premium-and-Ultimate-Overview

 The SharePoint 2013 comes with many  types of application development option.

this time SharePoint 2013 gives you a great sets of APIs to Development and build Apps for SharePoint 2013,webparts,Sharepoint Pages, Silverlight Applications  even on client computers or windows phone 7 & 8 devices . And asp.net based applications  will exposed in SP2013 by an Iframe,JS running on a SharePoint site page,a SharePoint application Page, a Microsoft .net framework application running on server or client. A power shells scripts, a timer jobs on SharePoint  server. And the best of of SharePoint 2013 you use your existing skills "JavaScript,ASP.NET,REST/OData,.NET Framework,Windows Phone,Silverlight,Windows PowerShell" to jump up and start development with SharePoint 2013 Apps.

    SharePoint  2013  APIs Improvements  

·         More Web Standards (Odata,Oauth)

·         More Client Side Support 

·         Improved Rest Model and EndPoint

·         Odata URL base Query Engine 

·         OAuth Web base identity system. 

·         Mobile Templates. 

New SharePoint 2013 Apps can run on server which can be a part of your SharePoint farm or external server, Cloud server ,Client devices… it’s very important to choose the right API for development for SharePoint 2013. In so many types application you can use multiple APIs. Hope so this article will help to understand SharePoint 2013 APIs .and selection of right API to developing app, and perform programmatically other SharePoint operations.

JavaScript object model

For example your create asp.net web App that performs simple CURD Operations or using SharePoint Data or external content type. Use JavaScript client object model. For better safe and fast performance.

As like Client Object Model with Managed Code Libraries in SharePoint 2013. you have JavaScript infrastructure in SharePoint 2013 work. interact form server in batches. Batches will asynchronously with SharePoint. SharePoint 2013 comes with new possibilities. In SharePoint 2013 by using JavaScript Libaries.  you can access the SharePoint Data across Domain. exmaple in JSOn. JavaScript  object model is defined in a set of *JS file in every server.

at %ProgramFiles%\Common Files\Microsoft Shared\web server extensions\15\TEMPLATE\LAYOUTS

Client object models  for managed code with  .net framework.

But in case if you does not have to call SharePoint across a firewall then you have to use (.NET Framework client object model or  Silverlight client object model, or REST/OData endpoints).

Silverlight client object model and Mobile Client Model.

 Silverlight Client object is mostly used with Windows phone 7 development and End to End Application. 

  for example you have to create some mappinng Application like bing maps or GIS based Applicaiton. 

  So you can use Silver-light  Client Models. 

 Mobile Client Model.

If you have create a Windows Phone 7 or windows Phone 8 Apps by using your SharePoint Data and perform CRUD Operations  with metro UI.  Then We have to go with SharePoint Mobile Client Object Model. But in same windows Phone application  we have to show calendar meeting  alert or any other information by using windows Phone Push notification.  then will use

Mobile client object model with the server object model.

Server object model

But if we are working with Administrative tasks like timer job, and other SharePoint administrative, custom Power Shells Commands,SP extension ,Custom Web Part or you have to installed something in GAC. For these kind of tasks SharePoint offer you the Server Side Object Model. Because you need a  strong Object Model and Managed classes off complete SharePoint Objects.  But Server Side Object Model cannot use in SharePoint App. Because by using Server object model you can create Custom logic which can disturb SharePoint Farm and clouds.

For example we have to create applications to perform  SharePoint CRUD Operation  for deferent Mobile Phone Platform like android ,iPhone,black barry … then we have to use REST/OData endpoints.

REST/OData  (More web standard for Developer play with SharePoint object in their application with rest endpoint which exposed by  Wcf dataservice. With OData standards and strong Brower base query syx)

WFC Data Service Reference

http://msdn.microsoft.com/en-us/library/cc668792.aspx

Example

http://msdn.microsoft.com/en-us/library/jj164022(v=office.15).aspx

Rest vs OOP

Feature	.NET Framework or Silverlight object models	JavaScript object model	REST/OData endpoints called from a Windows platform or JavaScript
Object-oriented programming	Yes	Yes	No
Batch processing	Yes	Yes	No
APIs for conditional processing and exception handling	Yes	No	No
Availability of LINQ syntax	Yes	No	No
Combining list data from different SharePoint web applications	Yes	No	Yes
Familiarity to experienced REST/OData developers	No	No	Yes
Similarity to non-Windows programming or JavaScript programming	No	Yes	Yes
Strong typing for list item fields	No (except with LINQ)	No	Yes, from Windows platform No, from JavaScript
Leveraging jQuery, Knockout, and other JavaScript libraries	No	Yes	No, from Windows platform Yes, from JavaScript

Reference

http://msdn.microsoft.com/en-us/library/jj164060(v=office.15).aspx

.NET Framework (strong Object Model with the Power of C#,vb.net,linq)

By
Baraah

I had such great time with MVPs  Joel Oleson, Michael Noel, Abdul-Hafeez Jamali, John Anderson, Eric Harlan, Sohail Hanif Baloch Madridista, Paul J. Swider, Mark Miller,