A simple upgrade…

Sometimes we still have to support some legacy code. And provider-hosted apps in SharePoint are one of the pains we still have to maintain. Since the announcement of Microsoft to only allow TLS 1.2 connections to Office 365 starting June 2020 we started to update legacy provider-hosted apps.

With releasing the SPAdminBot almost a week ago, I got some great response. But I also forgot to mention some items in my previous blog post. The steps to take on how to install this in your own Azure environment and use your own bot ID’s. In this post, I will go through the detailed steps on how to get the SPAdminBot up and running.

I’ve started a new open source project called the SharePoint Admin Bot or SPAdminBot for short. Why you ask? Because I got tired of doing and seeing people do the same tasks over and over again on SharePoint Online and Office 365. For something simple like creating a site collection you would always have to go into the admin portal and click through multiple pages to get the job done. These kinds of simple tasks can be easily done by a bot.

When setting a userprofile property backed by a term set in CSOM we use this snippet (sample from Office Dev PNP)

This is already the 5th part of our series. In this post will install SharePoint 2010 on our development environment. To shake this up a little lets not install this like we installed SharePoint 2013 but let’s use AutoSPInstaller (http://autospinstaller.codeplex.com/). You can also use this for the installation of SP2013 of you like.

This is the 4th series of my post on how to set up a SharePoint Hyper-V virtual farm. In the previous posts we prepared our different servers, installed SQL and SharePoint 2013. In this post we will configure SharePoint 2013 with PowerShell. Like i already said in the previous post there will be some benefits of doing it this way. If you use the standard configuration setup wizard then SharePoint will create the databases and services for you. This also means that you don’t have control over their names, passwords or the accounts they run under.

This is the third part of my blog post on how to set up a development farm for SharePoint.

This is the second part of my post how to set up a SharePoint development Farm. The first part can be found here Part 1

There are a lot of blogs out there describing how to setup a development environment for developing SharePoint solutions and with the new version of 2013 also the development of apps. Because of the improved capabilities in Windows 8 and Hyper-V I am converting all of my previous vmware virtual machines to Hyper-V. But what about my starting virtual machine where I begin a new project with? Well instead of converting that one I’ve set out to create a new SharePoint development farm.

In SP2013 the datasheet view is no more. It’s now been replaced with “Quick edit”