I am working on a project, using open-source development techniques, similar to the SharePoint Framework (i.e. using Node.js, Gulp, SASS, Typescript and Angular) to aid my development of a SharePoint-Hosted app.
When working in Visual Studio 2015 (with update 3) with Node.js tools installed, I needed to re-install the NPM modules and found after this, the Gulp Tasks are not loaded properly showing the following error:
On May the 4th Microsoft announced a new development framework for SharePoint, based on pure client side technologies. This framework would be utilising a combination of Node.js, Gulp, TypeScript, React and Knockout. It marked a radical change to the way we develop apps using established open source frameworks for pure client side with SharePoint office 365 and eventually SharePoint 2016.
Yesterday (18th August) Microsoft announced the release of SharePoint framework in Preview: See announcement: SharePoint Framework Developer Preview Release. So we are going to create a new app with this framework.
In a recent scenario with a client, we started to notice that some apps created over a year ago have started to expire. After investigating the cause, the default lifetime for an Client ID and Secret is 1 year, Yikes!
Once this has expired your apps will stop working! It is worth knowing when these principles expire, so from the Microsoft articles we have extracted the PowerShell used to list when these apps could expire.
Prerequisites before running the script
- Microsoft Online Services Sign-In Assistant is installed on the development computer.
- Microsoft Online Services PowerShell Module (32-bit; 64-bit) is installed on the development computer.
- You need to be a tenant administrator for the Office 365 tenant where the add-in was registered with.
The code for listing apps and their expiry is fairly straight forward and much of it is provided on MSDN, we have made a few tweaks to output to CSV, for tenants with large amounts of apps.