Azure / Office 365 / SharePoint Development / Search
Some time ago I wrote a couple of articles about how you can automate the process of releasing your SharePoint Framework solutions. This was achieved by two custom Gulp tasks to upload the static assets and solution package and a complete Visual Studio Team Services build and release pipeline. This process already saved me a...Read More →
Since I wrote the article about how you could configure build and release pipelines in Visual Studio Team Services, I got a couple of people asking if it is possible to get different builds working on one tenant. When you build something with the SharePoint Framework and are ready to move from development (workbench) to...Read More →
If you ever created Gulp tasks which made use of arguments to specify certain configuration settings to be used during the execution. You probably made use of a module called yargs. The yargs module makes it easy to check if arguments are provided and to retrieve their values. If you are building your own custom...Read More →
Just a quick article about how you can let your Azure Function runtime know there was a problem during the execution. This is important when you are for example working with queue triggered functions. The default method to let your Azure Function know it has finished is the context.done() method. When you use the method...Read More →
