tag:blogger.com,1999:blog-4126985520350746834.post782185983266899882..comments2024-03-28T07:00:21.554+00:00Comments on Chris O'Brien: SharePoint 2013 apps – architecture, capability and UX considerationsChris O'Brienhttp://www.blogger.com/profile/10022906552670607366noreply@blogger.comBlogger20125tag:blogger.com,1999:blog-4126985520350746834.post-48138780511666243742015-09-03T16:17:46.689+01:002015-09-03T16:17:46.689+01:00@Nancy,
Unfortunately I don't believe this is...@Nancy,<br /><br />Unfortunately I don't believe this is possible - Site Owners have permission to install apps/add-ins from the Store, in addition to Site Collection admins. This is very much the model, and I don't believe it can be changed (e.g. by tweaking the permissions for the Full Control permission level).<br /><br />Have you considered the "app requests" option? This means that even site owners can only *request* apps, and you are therefore able to apply some governance to which apps get used in your environment.<br /><br />Cheers,<br /><br />Chris.<br /><br />Chris O'Brienhttps://www.blogger.com/profile/10022906552670607366noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-82754312396914687602015-09-03T12:19:31.579+01:002015-09-03T12:19:31.579+01:00Great article. I was hoping you could help me clar...Great article. I was hoping you could help me clarify something I have not been able to find any clarity on as I look into whether our company will allow access to the App Store. It's about what end user role is allowed to install an app.<br /><br />We do not want ANY user below Site Collection Admin to be able to access the app store and install an app. Is this possible to configure in Central Admin? If not, how can we get this result?Anonymoushttps://www.blogger.com/profile/10083362496601427701noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-27040585892584492462015-04-14T10:36:25.785+01:002015-04-14T10:36:25.785+01:00Hi,
Is there any gallery where we can access all ...Hi,<br /><br />Is there any gallery where we can access all the app parts similar to web parts in web part gallery?<br /><br />We have a requirement where we need to list all the app parts (with their properties). This has to be done using CSOM. But we cudnt find any gallery or location from where we can read them programmatically. The only place we see them is when we edit a page to insert an app part.Juhihttps://www.blogger.com/profile/08100696189222021088noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-10863877055086168452013-08-13T11:28:20.303+01:002013-08-13T11:28:20.303+01:00Great series of articles, Chris - do you happen to...Great series of articles, Chris - do you happen to know anything about when it will be possible to submit Autohosted apps to the Marketplace? At the moment it isn't available.Johnnyhttps://www.blogger.com/profile/05350292169768591884noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-66111050569552317512013-02-20T18:52:17.707+00:002013-02-20T18:52:17.707+00:00Hello,
What do you think about the following idea...Hello,<br /><br />What do you think about the following idea:<br /><br />Create a normal webpart that is perfectly programmed. All it does is allow you to select an App in the App web in the webpart properties.<br />Then it shows the app-page that is in the app web in an iFrame on any regular publishing page.<br /><br />The advantages would be:<br />1) that you only have to deploy the code of that App-wrapper webpart.<br />2) it would allow site owners and contributors to securely add new functionalities by adding new apps, that are then wrapped in a webpart. 3) The apps' data can all be stored in the app web and it doesn't need to have permissions outside of the app web.<br />4) For end-user a sharepoint site works the same as before (i.e. statis + dynamic content).<br /><br />The downside is that you'd be immediately violating the app principle and you'd need a separate server for the small amount of farm-deployed code.<br />Jurgen Wiersemahttps://www.blogger.com/profile/08710765001789781772noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-74143504215015818422013-02-01T02:44:49.635+00:002013-02-01T02:44:49.635+00:00Hi Chris,
Do you know if it's possible to cus...Hi Chris,<br /><br />Do you know if it's possible to customize the small icon that appears in Edit Page > Insert > App Part? <br />Keith Tuomihttp://yalla.itgroove.netnoreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-18707773898867980282013-01-16T15:44:41.070+00:002013-01-16T15:44:41.070+00:00@Kourosh,
It sounds like you haven't configur...@Kourosh,<br /><br />It sounds like you haven't configured your app domain properly. Check out <a href="http://technet.microsoft.com/en-us/library/fp161236(v=office.15).aspx" rel="nofollow">Configure an environment for apps for SharePoint (SharePoint 2013)</a> on TechNet.<br /><br />HTH,<br /><br />Chris.Chris O'Brienhttps://www.blogger.com/profile/10022906552670607366noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-49857458021948077182013-01-16T11:38:47.211+00:002013-01-16T11:38:47.211+00:00Hi and thanks for this useful post.I have a proble...Hi and thanks for this useful post.I have a problem and hoping you can help med to solve it. I have created a SharePoint hosted app based on the template which is in VS 2012. I add nothing to it. When I hit F5 it works but when I publish it (adding .app file to app-catalog site collection) and add it to a site collection and browse to it, it says "This page can't be displayed make sure the web address http_mysite is correct. blah blah. Thank you alot.Kouroshhttps://www.blogger.com/profile/01296076723650856723noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-27533549006081944522012-09-30T22:18:45.346+01:002012-09-30T22:18:45.346+01:00@Natalia,
Main article text now updated, thanks a...@Natalia,<br /><br />Main article text now updated, thanks again for the prompt :)<br /><br />Chris.Chris O'Brienhttps://www.blogger.com/profile/10022906552670607366noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-49512308256208347212012-09-30T15:13:25.761+01:002012-09-30T15:13:25.761+01:00@Natalia,
You're absolutely correct - I actua...@Natalia,<br /><br />You're absolutely correct - I actually talk about this a lot in my next article <a href="http://www.sharepointnutsandbolts.com/2012/09/sharepoint-apps-working-with-app-web.html" rel="nofollow">Working with the app web, and why you should</a>.<br /><br />The idea of apps which have, say, a Manage Web permission request for the host web (or even Full Control to the host site collection) and use stuff there came to light (for me) between writing this article and that one, but I hadn't got round to correcting this one yet.<br /><br />Thanks for the comment, appreciate it!<br /><br />Chris.Chris O'Brienhttps://www.blogger.com/profile/10022906552670607366noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-60834503836201508512012-09-28T19:57:13.656+01:002012-09-28T19:57:13.656+01:00Correction on:
An app is effectively scoped to a w...Correction on:<br />An app is effectively scoped to a web only – the client APIs do not provide the ability to talk to the parent site collection, web application or farm<br /><br />You can talk to host web (spweb) or event site collection (SPSite) via APPS in case you have asked permission to access it.<br /><br />But for web application and farm, yes, it's correct. You can't get access to it even with ReadAnonymoushttps://www.blogger.com/profile/11256832116859571359noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-79544060739029511902012-09-18T11:19:51.113+01:002012-09-18T11:19:51.113+01:00@Anonymous,
That's a great clarification, tha...@Anonymous,<br /><br />That's a great clarification, thank you! I had missed the fact that actually the app web is on a different domain for HTTP request processing, but in storage terms it's actually in the same site collection. This makes more sense in terms of capacity planning etc.<br /><br />I'll update the main article text shortly. Thanks again.<br /><br />Chris. Chris O'Brienhttps://www.blogger.com/profile/10022906552670607366noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-55276729516220446262012-09-18T03:10:47.571+01:002012-09-18T03:10:47.571+01:00It seems like you have confirmed earliar in the co...It seems like you have confirmed earliar in the comments - Azure auto-hosting is only available in SharePoint Online.. Never mind...Nik Patelhttp://nikspatel.wordpress.com/noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-11887745752749672902012-09-18T03:08:57.739+01:002012-09-18T03:08:57.739+01:00I am trying to confirm from many sources and yours...I am trying to confirm from many sources and yours seems only resource mentioned this.. Azure auto-hosting is only available to apps deployed to SharePoint Online.<br /><br />Is that true? Auto-hosted Apps are available only in SharePoint Online? Only provider/developer hosted and SharePoint hosted Apps are available for On-premises?<br /><br />NikNik Patelhttp://nikspatel.wordpress.com/noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-25451734113542864192012-09-17T23:33:38.637+01:002012-09-17T23:33:38.637+01:00Nice post. One clarification: The app web is not i...Nice post. One clarification: The app web is not in a separate web application from the host web. In fact, it is a subweb of the host web, and thus it is the same site collection and content database. The app web a different base URL from the host web because it has its own domain name. This is for security reasons. For more information see this SDK topic: http://msdn.microsoft.com/en-us/library/fp179925(office.15).aspx<br />In fact, if you open Site Settings on the host web and then click the Site Hierarchy link, you'll see the app webs listed as subsites.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-4287846771622189472012-08-16T15:11:12.665+01:002012-08-16T15:11:12.665+01:00@Andrew,
Yes and yes. It would be entirely possib...@Andrew,<br /><br />Yes and yes. It would be entirely possible to host external components in Azure but not take advantage of auto-hosting for deployment. Indeed, auto-hosting may not make sense in some scenarios.<br /><br />So long as the external site (in Azure or elsewhere) can call into SharePoint via CSOM/REST etc., it's a workable option for app hosting.<br /><br />Cheers,<br /><br />Chris.Chris O'Brienhttps://www.blogger.com/profile/10022906552670607366noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-79235863685935099782012-08-16T14:05:13.873+01:002012-08-16T14:05:13.873+01:00So, Azure auto-hosting is only available in ShareP...So, Azure auto-hosting is only available in SharePoint Online - but would it be possible to use Externally Hosted Azure application? Just that would seem to solve many of the questions around externally hosted - except, of course, that your SharePoint farm would need to be able to access the external host.<br /><br />Would that be possible? Does that make sense?Anonymoushttps://www.blogger.com/profile/07504025809795400522noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-64049711156494902642012-08-08T04:33:23.561+01:002012-08-08T04:33:23.561+01:00Useful information shared..I am very happy to read...Useful information shared..I am very happy to read this article..Thanks for giving us nice info. Fantastic walk-through. I appreciate this post.Anmolhttps://www.blogger.com/profile/10142507373363600908noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-71076561593446598492012-08-01T13:36:02.663+01:002012-08-01T13:36:02.663+01:00@levalencia,
Thanks. Those are all good questions...@levalencia,<br /><br />Thanks. Those are all good questions. Let me try to answer:<br /><br />1. Yes, the artifacts are in a different site collection and content database. See my image with the stacks of dollars - notice the URL is to a different web application.<br /><br />2. Yes and no. Apps are isolated, so they cannot access data provisioned by other apps. However, an app may be able to access data in the 'host web' - e.g. OOTB list/libraries which the users use. This is what the site owner must agree (the app permission request) when he/she installs the app to the site.<br /><br />3. Apps have their own upgrade lifecycle. I haven't yet looked at this in detail, but I am expecting that upgrades to SharePoint artifacts in the app web would indeed be handled by the Feature Upgrade framework. I'll follow up on this in future articles.<br /><br />Thanks!<br /><br />Chris.Chris O'Brienhttps://www.blogger.com/profile/10022906552670607366noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-37082349768255837652012-08-01T09:58:25.918+01:002012-08-01T09:58:25.918+01:00I really love this post because it shows the hidde...I really love this post because it shows the hidden disadvantages of Apps, After reading this post however I have a few questions:<br /><br />You say:<br />Any SharePoint artifacts provisioned (lists, web parts, content types, site columns, master pages, content pages, other files) do not get provisioned in the site end user browses <br /><br />So, where are the lists stored? In a different content database?<br /><br /><br />2nd. If artifacts provisioned are not in the site the end user browse, so I suppose you cant access lists created by other apps, or OOTB lists in the sharepoint site?<br /><br /><br />I am still thinking that for corporate development, webparts/farm solutions will be the way to go.<br /><br /><br />3rd. After reading your feature upgrading posts many times, I must ask, Apps can be upgraded the same way? What about if you create version 1.0 of an app with 3 fields, and later you need to add another 2 fields in version 2.0?Anonymousnoreply@blogger.com