A couple of months ago I wrote an article about the new look of SharePoint 2013, focusing on the new Site Collection themes for SharePoint. I gave a couple of examples for the new built-in themes included in SharePoint 2013.
As you know SharePoint 2013 introduces a new development model, known as the App Model, that allows you to create and deploy applications for SharePoint On-Premise and SharePoint Online in Office 365. If you want to know more about how to build applications for SharePoint, I recommend you to visit the Build apps for Office and SharePoint portal created by Microsoft. There you can find a lot of useful information and resources about this new development model, how to build apps, and so on.
Microsoft recently released the RTM version of the Microsoft Office Developer Tools for Visual Studio 2012 (read the announcement on S. Somasegar’s blog) as a step forward in their development support for SharePoint and Office 2013. In this article, I will explain how to install the final version of the tools in a CloudShare environment where Visual Studio 2012 + Preview 2 of the Office Developer Tools is installed.
Read-Only Databases is a feature available when upgrading or moving SharePoint 2013 content databases to avoid any data loss and allow users access to the information stored in the system. In this mode we can backup content databases with the latest information available, and at the same time guarantee our SharePoint users can read existing data, but not modify it. In this article, I will explain step-by-step how to configure an existing content database in read-only mode:
I restarted my SharePoint server, opened Central Administration and encountered the following error:
Server Error in ‘/’ Application
Description: An application error occurred on the server.
Workflows are another key area in SharePoint 2013 where Microsoft has made great investments. In fact, workflow platform is completely new in that it allows creation, usage and deployment of .NET Framework 4.x workflows in a SharePoint 2013 farm. Microsoft has completely redesigned the workflow platform for SharePoint by creating the Windows Azure Workflow Server (WAS) that enables us to completely separate the SharePoint side from the workflow one. Indeed, workflow infrastructure in SharePoint 2013 is completely independent from the SharePoint point of view that consumes and uses workflows through a web services façade.
Access and Manipulate Data in Your CloudShare SharePoint 2013 Farm from Anywhere with CSOM, REST and ODataDecember 16th, 2012 | Author: Danny Jessee | Filed under: CloudShare, Dev / Test, SharePoint | Tags: CloudShare, CSOM, OData, SharePoint, SharePoint 2013, SharePoint Configuration
SharePoint 2010 introduced the client-side object model (CSOM) to allow developers to write applications which interact with SharePoint from client-side code. In SharePoint 2013, Microsoft steps things up a notch by allowing developers to use Representational State Transfer (REST) in conjunction with the Open Data (OData) protocol to perform Create/Read/Update/Delete (CRUD) operations against SharePoint sites and lists for nearly every API in the CSOM. Through the magic of CloudShare web access, we can leverage the CSOM along with REST and OData to interact with our SharePoint 2013 environments from literally anywhere, using any type of client! All code samples in this blog post will be run from my local workstation over 1,000 miles away from my SharePoint 2013 server running in the CloudShare datacenter!