I'm looking for best practices on provider hosted application lifecycle management and tips on how to structure projects in visual studio solution for multiple provider hosted Apps. The scenario is that we will have quite a few SharePoint Apps and all of them will be provider-hosted Apps. The AppWeb will be deployed either on a web server owned by us, or as Windows Azure web sites (which is preferred). These apps will need to be made available in both On-premise and SharePoint Online.
We want to save cost by having all AppWebs underneath one IIS web site (or one Azure web site role). Underneath the web site we will have virtual directories that correspond to each AppWeb.
- Is this feasible?
- Has anyone done this elsewhere?
- What is the recommended approach?
- How to structure Visual studio solution for App if we were to use one web site for all of the AppWebs? Is it one sln for all Apps across the organisation, or can we still have one sln per App?
- How about pre-production environments? Can Build target let us deploy to these different environments? Anybody has scripts they can share for this?
