There’s a lot of buzz nowadays about moving to Office 365 and using the App Model to extend and customize the platform. However, I know a lot of folks aren’t even considering Office 365 just yet, so I was wondering how are you developing “Apps” internally?
Are you using Full Trust Farm solutions? Or, are you starting to create Apps internally? I am guessing the decision points will be based on the fact that Farm Solutions are far quicker to develop, but harder to migrate in the future. Whereas “Apps” are slow to develop but set you up for a potential move to Office 365…
Love to hear your thoughts…
>>Colin – fantastic response. At Collaboris, we have been struggling to put together a few “simple” templates using declarative mark-up only. Workflow has been the biggest barrier and pain point. It’s taken way too long and has cost a fortune. In the time the devs have been on that, I have managed to create and publish 3 new Workdpress sites!Â
Microsoft and PnP “officially” suggest to do a code based provision. That’s it. MVPs nowadays tell everyone how to do that, people at MS promoting that as well as promoting “remote provisioning pattern”, that’s how they call it 🙂 XML/WSP was not a good options not in 2007, not in 2010. That’s the other discussion, but simply sayin WSP/XML don’t fit a proper ALM process, have to much limitation and can hardly be tested (ALM again).Â
SP2013 workflow can be provisioned via code. An API is there, all good. SPMeta2 simplifies provisioning, as well as was able to do workflow that for quite a time, plus there are samples in various blogs.
>>We are currently re-architecting DocRead for Office 365 and it’s going to be tough, but we are taking the approach to use as little SP functionality as we can.Â
Tough! Really tough, guys. But keep it up, we will be there.
