Step 1: Create a list-based autohosted app in SharePoint 2013

In Visual Studio 2012, create an App for SharePoint 2013 project from the Office SharePoint, Apps node (under either C# ) in the templates tree of the New Project wizard. Choose the Autohosted hosting option. In the continuing example of this article, C# is used as the language and SupportCenter is the project name.

Choose Finish in the wizard. A lot of configuration is done when the solution opens. The following are some of the most important things that occur.

• Two projects are created in the Visual Studio 2012 solution: one for the app for SharePoint and the other for the ASP.NET web application.

• The Web Project property of the app for SharePoint project is set to the name of the web application project.

• The values in the AppManifest.xml file are set appropriately for an autohosted app. The Start Page URL is set by default to ~remoteAppUrl/Default.aspx replace this with ~appWebUrl/Pages/Default.aspx?{StandardTokens}. The Query String value is set to {StandardTokens}. This is also a token that resolves to a longer query string that includes an identification of the URL of the SharePoint website to which the remote web application communicates. Because neither the host web nor the app web URL is known until the app is installed, you need to use a token as the value of the query string. For more information about tokens in the app manifest, see App for SharePoint manifest file and URL strings and tokens in apps for SharePoint.

• The Target Framework of the web application is set to Microsoft ASP.NET 4.0 (not Microsoft ASP.NET 4.5).

• The SSL Enabled property of the web application is set to True.

• References are added to the web application project for the SharePoint client object model assemblies as well as assemblies for the Microsoft identity model infrastructure.

• A source file named TokenHelper.cs or TokenHelper.vb is added to the web application project.

In Solution Explorer, choose the node that represents the project (named SupportCenter if you follow the naming convention used in these procedures).

On the Project menu, choose Add, New Item. When the Add New Item dialog box opens with the Office/SharePoint templates, choose List.

Specify Technicians as the name of the list, and choose Add. In the SharePoint Customization Wizard, choose customizable list based, and then choose Default (Blank) from the drop-down list.

After you add the list to the solution, you can add a column to the list using the user interface.

In the Solution Explorer, choose the node that represents the newly created list (named Technicians if you follow the naming convention used in these procedures). Open the selected node to open the Technicians list in the List Designer, and add the columns and field types shown in Table 1. Delete the columns that are created with the list before you add new columns to the list.

Repeat step 4 to create one more list with Notifications as the name of the list in your app for SharePoint.

Repeat step 5, and use Table 2 to create columns in the list Notifications created in the preceding step.

To add the third list in your app for SharePoint, repeat step 4. Specify Cases as the name of the list, and choose Add. In the SharePoint Customization Wizard, choose customizable list based, and then choose Tasks from the drop-down list.

In the Solution Explorer, choose the node that represents the newly created list (named Cases if you follow the naming convention used in these procedures). Open the selected node to open the Cases list in the List Designer, and add one column to the existing columns Customer Address as the Display name and Multi Lines of Text as the field type for the column.

In the AppManifest.xml file, add the following code. To learn more about Permissions, see App permissions in SharePoint 2013

<AppPermissionRequests>
    <AppPermissionRequest Scope="http://sharepoint/content/sitecollection/web" Right="FullControl" />
  </AppPermissionRequests>

In the Solution Explorer, choose the node that represents the newly created list (named SupportCenter if you follow the naming convention used in these procedures). Add a .aspx page to the solution.

Add the following code inside the body of the page

<div>
        <p>
            <table cellpadding="20">
                <tr>
                    <td valign="top" align="left">
                        <p>
                            <a href="../Lists/Cases">Support Cases</a>
                        </p>
                        <p>
                            <a href="../Lists/Technicians">Technicians</a>
                        </p>
                        
                        <p>
                            <a href="../Lists/Notifications">Notifications</a>
                        </p>
                        
                    </td>
                </tr>
            </table>
        </p>
    </div>

In Solution Explorer, choose and expand the node Features.

In the feature designer, expand the Feature Activation Dependencies node, and then choose the Add button.

In the Add Feature Activation Dependencies dialog box, choose the Add a dependency on features in the solution option button, enter Push Notifications in the title of the feature you are adding as a dependency, enter 41e1d4bf-b1a2-47f7-ab80-d5d6cbba3092 in the feature ID text box, and optionally add a description. Then choose the Add button.

To learn more about adding a feature, see How to: Add and Remove Feature Dependencies.