There are lots of reasons to take a step back and really consider your on-premises SharePoint farm – frustrated users, poor performance, random errors and outages, out of control content, etc. – but often we find ourselves overwhelmed with the sheer scope and size of SharePoint, and the idea of doing a health check just seems daunting; there are so many moving parts and so many different ways to achieve the same thing, and with every different way to configure SharePoint there are probably a dozen different opinions on whether this way is better than that way, and it’s difficult to sort through all the “guidance.” Most people have only their own farm(s) as a point of reference, so they don’t have the benefit of personal experience working with a variety of different farms serving different purposes (and often exposing very different issues).
I’ve been pretty slow to learning how to use github for the management of my open source projects but I’ve finally managed to take the time to at least learn enough so that I could move my main projects over. I don’t know that I’ve got everything done exactly the way it should be as I kind of stumbled through it a bit but I think what I’ve got so far should be a good start for anyone who wants to download the releases or see or contribute to the source.
Gary writes about how to load the CSOM assemblies into memory, and then introduces a simple helper function that you can utilize to quickly get connected to a SharePoint Online Site Collection.