Hi,
I´m wondering if someone has some hands on experience with working with provider hosted apps with multiple developers and can share some of your work methods.
The only way I have currently tested is working on my local machine with a copy of the source code, and each developer has an own site collection for debugging and testing. The problem with this approach is that it creates challenges with the data that should be equal on all of the development sites.
Hi Frank,
I would say it is the same rules as in general development.
Provider hosted app is hosted in its own server (azure, on site internet facing server, other hosting center) and is it built with .NET? Does not matter much what stack it is built on, but with MSDN subscription you have access to developer licens for Azure. You could also share one Azure account with one web application per developer and one for SIT, one for FT, QAT & production. Depending on the size of the team and complexity of the application you are building.
Model the application and divide the task user stories/tasks by component/class with clear interfaces or i.e. functional requirement areas.
Package it as a sharepoint application you can do at any point (maybe last) and verify how you deploy/distribute it and how it fits into the portal etc.
BRs,
M
