<body><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener('load', function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <div id="navbar-iframe-container"></div> <script type="text/javascript" src="https://apis.google.com/js/plusone.js"></script> <script type="text/javascript"> gapi.load("gapi.iframes:gapi.iframes.style.bubble", function() { if (gapi.iframes && gapi.iframes.getContext) { gapi.iframes.getContext().openChild({ url: 'https://www.blogger.com/navbar.g?targetBlogID\x3d8211560\x26blogName\x3dTech+Tips,+Tricks+%26+Trivia\x26publishMode\x3dPUBLISH_MODE_BLOGSPOT\x26navbarType\x3dBLUE\x26layoutType\x3dCLASSIC\x26searchRoot\x3dhttps://mvark.blogspot.com/search\x26blogLocale\x3den\x26v\x3d2\x26homepageUrl\x3dhttp://mvark.blogspot.com/\x26vt\x3d601588505461698440', where: document.getElementById("navbar-iframe-container"), id: "navbar-iframe" }); } }); </script>

Tech Tips, Tricks & Trivia

by 'Anil' Radhakrishna
An architect's notes, experiments, discoveries and annotated bookmarks.

Search from over a hundred HOW TO articles, Tips and Tricks

Overview of SharePoint 2013

Notes from the Pluralsight course SharePoint 2013 Developer Ramp-Up - Part 1:
  • Significant changes in SharePoint 2013:
    • New development model - SharePoint Apps - ideal for Office 365, App Marketplace
    • Minimal Download Strategy (MDS) UX
    • Web Apps support claim based authentication by default
    • Architectural changes:
      • Workflow
      • Search
      • Web content management
    • Deprecated capabilities
    • SharePoint Designer's Design view
    • Meeting & Document Worksapces
    • BI: Chart Web Part, Status Indicators & Status Lists
  • An app can contain a solution. A solution can contain one or more features
  • A *.app file is a .zip file containing a package of files. Contains a manifest file.
  • Server-side code is completely inaccessible inside an App
  • Sharepoint 2013 deployment options:
    • On-premises (behind firewall)
    • Hosted aka Office 365/Sharepoint Online
    • Hybrid - mix of On-premises & Hosted
  • SharePoint 2013 won’t work on a client OS; needs Windows Server 2008 R2 SP1(x64 only) or Windows Server 2012(x64 only)
  • You have to explicitly load SharePoint Windows PowerShell snap-in from console or script
  • Sandboxed solutions retained for backward-compatibility; will work on on-premise and hosted modes
  • SharePoint-hosted apps will work on on-premise and hosted modes
  • Provider-hosted apps will work on on-premise and hosted modes
  • Farm solutions will only work in an on-premises deployment
  • Autohosted apps will only work in a hosted deployment
  • SharePoint Client-side Object Model, introduced in SharePoint 2010, has significantly expanded coverage
  • JavaScript, unlike other languages, can be used for all deployment types - farm solution, sandbox solution, App (SP-hosted), App (Provider/auto-hosted)
  • What you are building dicates the type of local development environment you need
  • SharePoint-hosted apps can be built with Office 365 Napa app. 
  • Napa is a slimmed down web-ified version of VS
  • It supports client-side code only and provides a markup view for ASPX pages. Code-behind is not allowed
  • All Office 365 developer sites have an unlimited license to the "Napa" app. It is available in the online SharePoint Store for free
  • Napa can open the app in a local instance of Visual Studio 2012 to take it to the next level.
  • Solutions, Provider-hosted/auto-hosted apps can be built with Visual Studio 2012 + Office + SharePoint tools
Also see: Free Pluralsight videos


Tweet this | Google+ it | Share on FB

« Home | Next »
| Next »
| Next »
| Next »
| Next »
| Next »
| Next »
| Next »
| Next »
| Next »


Post a Comment