Office Development MVP / Office 365 & Azure Development
The preferred way to implement pipelines these days in Azure DevOps is via YAML. Which makes the pipeline part of your code and is automatically version controlled.
When you were used to the classic way of creating release pipelines, you might have used environment scoped variables. These scoped variables were great to specify to which environments you wanted to provision/install/deploy/… your solutions.
When creating solutions based on SharePoint search, you best always define the source ID of the Local SharePoint results source with each call. By providing that source ID with each request, you make sure that the results you expect for your solutions are always the same.
Which ID? The Local SharePoint results source ID you are looking for is: 8413cd39-2156-4e00-b54d-11efd9abdb89.
Last year I already wrote an article about how you could implement visual UI tests for your SharePoint solutions by using Puppeteer in combination with Jest. I still use these tools for setting up various UI tests in our products, but a couple of months ago, a tool called Cypress caught my attention.
WHAT A YEAR! This year was a personal rollercoaster. I would have never thought 2019 would be so hard, fun, crazy, and filled with a lot of life lessons.
Rollercoaster What happened in 2019? Initially, I told myself to do less travel in 2019, only attend a couple of events and focus a bit more on product development, family, and hobbies.
On SharePoint modern pages, you can set the focal point of the header image. Having this kind of control is excellent for creating compelling pages.
Header image with focal point What if you also want to make use of the same focal point in your roll-ups? Luckily this is also possible, and it depends a bit on how you retrieve the data.
