I think you already know about hosted approaches in SharePoint 2013. There are three types of hosted approaches (SharePoint-Hosted, Provider-Hosted, Auto-Hosted). There are similarities as well as differences. Thus there are slight differences in developing client app part in SharePoint Hosted Model.
This is a step by step guide to create a Client App part.
( If you looked closely, you can find out it is referring to jQuery 1.6.2 version that is quite old. So if you want, you can right click the project and go to NuGet Manager and install new version.)
-
Now we are going to add a Client App part. Client App Apart is a concept which allows to run SharePoint pages inside the iFrame. Therefore, you can theoretically display any page inside the client app part.
-
As a guide, I will show two types of Client App Parts:
- Simple App Part
- App Part with SharePoint
I separated these two of JavaScript usage. Most of the online sources talk about the simple app part, but when you try to use it with "SP.ClientContext
” ; it is giving errors.
Simple App Part
- Adding a client web part is same for both types. You need to right click the project and add a Client Web part with a desired name.
- When you do so, you will get a Client App Part with an element.xml:
- Element.xml is used for specifying rendering width, height, what page to point and define client app part properties (if any).
- Now, we need a page to point in the client app part. Thus, I'm creating folder under pages called
AppPart
(This is just to make it easy for you to put the page inside the page folder as well) and creating a page called Page.aspx.
- The page comes with two content place holders which are pointed to SharePoint master page. If you use this one, your app part pages will have SharePoint master page simply ribbon and all. Since we are placing client app part inside a page, we do not want ribbon and staffs in it. Thus, delete the entire content in the page.
- And put the following code to the page:
<%@ Page Inherits="Microsoft.SharePoint.WebPartPages.WebPartPage, Microsoft.SharePoint,
Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" Language="C#" %>
<%@ Register TagPrefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls"
Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c" %>
<%@ Register TagPrefix="Utilities" Namespace="Microsoft.SharePoint.Utilities"
Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c" %>
<%@ Register TagPrefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages"
Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c" %>
<WebPartPages:AllowFraming runat="server" />
<html>
<head></head>
<body >
<div>Simple Client App Part</div>
</body>
</html>
<WebPartPages:AllowFraming runat="server" />
this tag allows the page to run as an iframe. In the Url also DisplayType=iframe
allows to render like an iframe. You do not need to put both of them I just illustrate it for reference. - Now you are ready with the page. you need to give the page path to client app part. Thus you need to open the Element.xml in the client app and put the url there.
- When adding the url, you need to use
~appweburl
as a prefix to resolve the web url. - Now, you can deploy app to the SharePoint and see whether it is working.
App Part with SharePoint
-
If you are going to use SharePoint Client Context inside your Client app page, refer to the following JavaScript as well. (mQuery,sp.ui.dialog,callout
is commented because it may not be needed for you all the time)
<%@ Page Inherits="Microsoft.SharePoint.WebPartPages.WebPartPage, Microsoft.SharePoint,
Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" Language="C#" %>
<%@ Register TagPrefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls"
Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c" %>
<%@ Register TagPrefix="Utilities" Namespace="Microsoft.SharePoint.Utilities"
Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c" %>
<%@ Register TagPrefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages"
Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c" %>
<WebPartPages:AllowFraming runat="server" />
<html>
<head>
<link href="../../Content/App.css" rel="stylesheet" />
<script src="../../Scripts/jquery-1.6.2.min.js"></script>
<script type="text/javascript"
src="https://ajax.aspnetcdn.com/ajax/4.0/1/MicrosoftAjax.js"></script>
<script type="text/javascript" src="/_layouts/15/init.js"></script>
<%----%>
<script type="text/javascript" src="/_layouts/15/sp.runtime.js"></script>
<script type="text/javascript" src="/_layouts/15/sp.js"></script>
<%----%>
<script src="../../Scripts/App.js"></script> <%----%>
<script type="text/javascript">
$(document).ready(function () {
SP.SOD.executeFunc('sp.js', 'SP.ClientContext', function () {
});
});
</script>
</head>
<body>
</body>
</html>