In numerous projects I have seen development environments that resemble nothing like production. Only to result in a problematic transition through the ALM process, bugs caused by inconsistency, significant differences in SharePoint updates, configuration and even permissions.
I am not saying that you shouldn’t write your app to “expect a specific configuration” or to avoid best practices around handling configuration issues. However, to reduce issues down the line, as a minimum, environments should be setup with the following:
Restoring archived VMs, only to find that the trust relationship between the VM and AD has failed. This is an age old problem that I have encountered throughout my time working with VMs and SharePoint development environments.
I have found a great reference for fixing this issue by Thomas Balkeståhl and his blog post: Fix: The trust relationship between this workstation and the primary domain failed
The key take-away from this blog:
Have you ever wondered how Microsoft manage SharePoint Online?
Recently the Microsoft Ignite Conferences have released presentations showing how they have implemented such a large scale SharePoint/OneDrive platform across the world.
It truly is amazing to watch and marvel over the architecture:
I’d love to get hold of the machine learning software that auto-fixes environments 😉
I didn’t come by this during a random google, the new Microsoft Tech Community posted this in forum under ignite content. I highly recommend joining this community as this has now replaced the Yammer Group.