ElioStruyf GitHub Star | M365 Development, Developer Technologies MVP | Google Developer Expert Azure | Microsoft 365 | Visual Studio Code | End-to-End Testing

Along with acting as VP of BIWUG (Belgian Information Worker User Group), Elio is an independent contractor for his own consulting company, Struyf Consulting.

Passing arguments with custom Gulp tasks for SharePoint Framework projects

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 Gulp tasks for your SharePoint Framework projects, you do not require this module.

Read more

How to let an Azure Function know something failed

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 like this: context.

Read more

Configure a build and release pipeline for your SharePoint Framework solution deployments

In the previous article, I wrote how I achieved to setup a build and release pipeline to automate the publishing process of my SharePoint Framework app package and JS file to my environments. Info: Use build and release pipelines in VSTS to automate your SharePoint Framework deployments. In this article, I will focus on explaining the steps in detail how you can achieve it yourself.

Read more

Writing unit tests for your SharePoint Framework components

Last week I published a sample project on GitHub which shows how you can test your SharePoint Framework components with some predefined unit tests. Info: here is a link to the repo - https://github.com/estruyf/spfx-testing-wp The current sample is created with React. The unit tests are created only to test the actual component instead of the main web part.

Read more
Back to top