The purpose of this sample is to show the best way to declaratively include a Web Part on a page in the app web, because the best way is not the most obvious or natural way. Developers should not simply include WebPart markup in the ASPX page itself. Doing so can cause errors when the app is updated.
Instead, the WebPart markup should be in the element manifest file (usually called elements.xml) for the page.
- SharePoint Online and SharePoint on-premise
None.
| Solution | Author(s) |
|---|---|
| Core.WebPartOnAppWebPage | Ricky Kirkham (Microsoft) |
| Version | Date | Comments |
|---|---|---|
| 1.0 | January 31st 2015 | Initial release |
THIS CODE IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR NON-INFRINGEMENT.
- Open the .sln file for the sample in Visual Studio.
- In Solution Explorer, highlight the SharePoint app project and replace the Site URL property with the URL of your SharePoint developer site.
You can now run the sample with F5. You will not be prompted to trust the app because this is a SharePoint-hosted app and it automatically has full rights to the app web. The app will launch immediately and you will see the start page with a list view WebPart on it. There are no items in the list.
We'd love to get your feedback on this sample. You can send your questions and suggestions to us:
- In the Issues section of this repository.
- On Stack Overflow. Make sure that your questions or comments are tagged with either [Office365] or [SharePoint], and with [API].
Copyright (c) Microsoft. All rights reserved.