Hot answers tagged app
5
In addition to traditional web parts still being supported (in either full-trust or sandboxed solutions) as Simon mentions, you can develop new app parts in an app for SharePoint 2013.
An app part is like a web part, and in fact is also made available to users in a host web's web part gallery. Users add app parts to pages the same way they would add web ...
3
Lists in the app web are good for storing instance-specific app configuration data since a single app may have many instantiations across a farm.
Also, apps will always have full control over their app web so they are guaranteed to be able to read from, write to, and delete list items on a list in the app web. If a list were in the host web and the app ...
3
Yes, there are fundamental differences between SharePoint-hosted and cloud-hosted apps.
A SharePoint-hosted app may provision basic resources into its app web such as HTML/CSS/JS files, site column/content type/list definitions, etc. Under no circumstances can server-side code run within a SharePoint-hosted app.
You can run server-side code in a ...
3
Before you can deploy a SharePoint hosted app to your SharePoint Preview development environment you have to configure an isolated app domain.
like this :
http://sharepointchick.com/archive/2012/07/29/setting-up-your-app-domain-for-sharepoint-2013.aspx
http://msdn.microsoft.com/en-us/library/fp179923%28v=office.15%29
Hops it helps!!
2
You need to setup the app domain
this is a good tut but very lengthy
http://sharepointchick.com/archive/2012/07/29/setting-up-your-app-domain-for-sharepoint-2013.aspx
also this:
In order to install an App from the App Store you must setup an
isolated App Domain, this is because Apps from the store deploy to
their own app domain and run under a ...
2
Fun stuff, I was checking this site since I stopped answering SO SharePoint questions for a few years now and this was the first thing in the list, a very interesting oversight during the "host web Feature" option for CustomActions.
What a detailed investigation! Luckily I have a solution for you.
WEB STANDARDS TO THE RESCUE CHO CHOO
With Microsoft ...
2
If you plan to provision the page using a Module, I'd recommend configuring the web part inside of the Module, rather than in the aspx file itself. This will allow you to select whichever view you would want:
<File Path="mypage.aspx" Url="mypage.aspx" Type="GhostableInLibrary">
<View List="Lists/Personnel Holiday Entitlement" BaseViewID="4" ...
1
It is available on the App Web under
"The APPWEB URL"/Lists/"The list internal name"
But really you should access the list (CRUD items) via Client object model or REST.
The list is meant to be "hidden" to the users of the app, and it is upp to you to provide interfaces to work with items in the list
And just a clarification: You need to use ...
1
It seems that the problem arise when your master pages are not located in the Master Page Gallery. The problem went away when I added the master page to the master page gallery and referenced it from there (i.e. _catalog/masterpage/mymasterpage.master) instead of the _layouts folder. The actual server deployment location of the master page is still in the ...
1
You actually need to generate a SP.ClientContext for the app web and a SP.AppContextSite for the host web. To get a reference to a list in the host web, try the following:
// Get the ClientContext for the app web
clientContext = new SP.ClientContext.get_current();
// Use the host web URL to get a parent context - this allows us to get data from the parent
...
1
Is this what you're looking for?
http://blogs.msdn.com/b/richard_dizeregas_blog/archive/2013/03/10/leveraging-sharepoint-dialogs-in-apps-for-sharepoint.aspx
1
If you want to change it pro-grammatically check this link out. Where they getting the webpart and then setting it's view.
create or get XsltListViewWebPart
You can change default view in the definition of your list too.
Here's a similar question on SE that explains how to change list's default view in Schema.xml
1
If your SP app has a remote web in the solution, you can store the image in you remote app and use the token ~remoteAppUrl to correctly resolve the URL to that image.
For some reason MS wired up ~remoteAppUrl correctly but did not do the same for ~appWebUrl. Hopefully they will fix that in the future.
1
I didn't really expect anyone to "chase this down" for me, so I spent some time doing a lot of digging on my own. The short answer (as of January 2013) is "no" - there doesn't appear to be any way to leverage tokens like ~appWebUrl in the Image32by32 and Image16by16 attributes. The way that the image attributes are processed is inherently different than the ...
1
According to the comments on the site, step 6 which adds the user to the account, and sets the proper app pools is incorrect. I'd investigate that avenue and make sure the permissions are properly set to match that user account.
$account= Get-SPManagedAccount "domain\user"
$appPoolSubSvc= New-SPServiceApplicationPool -Name SettingsServiceAppPool -Account ...
1
You essentially want to use jQuery deferred methods and a promise to run something when the deferred is completed (or 'resolved').
Try this (you may need to modify sharePointReady() to return a a Deferred object instance):
<script type="text/javascript">
$(document).ready(function () {
SP.SOD.executeFunc('sp.js', ...
Only top voted, non community-wiki answers of a minimum length are eligible
