Today I was working on what seemed like a simple little task. I wanted to create a subsite using a REST call in SharePoint 2013. I’m not working in an “app” per se – this is for SharePoint 2013 on premises, and I want to do the subsite creation directly from a call in a plain old aspx page.
Outputting JSON using an XSLTListViewWebPart and some custom XSL.
This is the first in a 4 part series about JSLink where I intend to go through all the ins and outs of using Display Templates to customise list rendering.
SharePoint 2013 has a powerful new feature known alternately as JSLink (when working in SharePoint)and Client-Side Rendering, or CSR (in the Microsoft literature). Either way, the point is the same… this code runs on the client side, meaning after the page loads. […] Client-Side Rendering is pretty straightforward, but takes a little understanding of how the JSLink functionality performs in order to get things just right.
This article will cover the changes between how we used REST in 2010 and what we need to ‚update‘ for using the streamlined interface in SharePoint 2013.
When creating SharePoint 2013 apps, you often need contextual information about the app and the user. This contextual information includes things like the URL of the host web or the account claim of the current user. […] To solve the problem, I created 2 libraries for managing context: one for SharePoint-Hosted Apps (wingtip.context.js) and one for Cloud-Hosted Apps (wingtip.remotecontext.js).