Today we will see what the Project structure is for SharePoint Hosted Apps in Visual studio 2012 and significance of AppManifest.xml file.
· Features: This folder is used to deploy features to the server that's running SharePoint.
· Package: This folder is used to deploy the solution to the server that's running SharePoint.
· Images: This folder is used in the app for SharePoint project, such as icons or screenshots.
· Pages: This folder contains .aspx or .html pages that are used in the app for SharePoint project.
· Content: This folder contains any .css style sheets that are used in the app for SharePoint project.
· AppManifest.xml: Defines the various elements of the app for SharePoint project.
AppManifest.xml is an important file in the project, which describes various properties of App and how it behaves in SharePoint 2013. The properties are Title, Start page, Permissions, Feature prerequisites, capability prerequisites.
If you open the AppManifest.xml by Right click on the file and Open with XML (Text) Editor.
You can see the details of configuration in XML editor format.
The above screen “Name” property is Name of the SharePoint App.
“Product Id” is Unique Identifier of the SharePoint App, it doesn’t change with the versions.
“Version” is version of the SharePoint App.
“SharePointminimumversion” is the minimum version of the SharePoint with which the app compatible with.
“AppPermissionRequests” this specifies what are all the resources required by the app.
In the above screenshot shows the list of scope that SharePoint hosted App can support, different scopes have different levels of permissions. Example BCS will have only Read and Write Permissions.When you deploy the App to SharePoint by setting the permissions it will ask the user who is deploying it to SharePoint “DO you trust ‘Appname’”. User can select “Trust” or Cancel. If Trust is selected it will get added to the SharePoint hosted site
AppPrerequisites property can add list of features and capabilities that are required to support the App.
SharePoint-Journey for Administrators, Developers and users