.NET, Azure, and Office dev
Previously I was tasked to ensure all of our micro-services were set up correctly with distributed tracing, although there were a lot of docs that mentioned the topic and gave some insight, none gave straight information on how it worked. Below details some things that would have made my job a lot easier if I... Continue Reading →
One of the common issues among developers in our organisation is the notifications from Azure DevOps. We get so many that they often go unnoticed or ignored, which leaves others waiting for responses to a Pull Request. I have compiled up a few hints to help reduce the torrent that is Azure DevOps Notifications.
TL;DR: Azure Front Door's Health Probes can cost you quite a bit.
I have been developing a backend service that requires a Microsoft Graph token passed up from the frontend. During this development, I have been using Postman to do the call, and have used a simple SPA with authentication to give me a token to my development tenant. This has been a pretty annoying way to do things when the token expires every half an hour or so, meaning I need to generate another.
The Microsoft Graph Documentation on how to update a SharePoint list item describes only how to update the fields. But what if you want to change the content type?
You may have come across the Files tab for a channel in Microsoft Teams. This basically shows the contents of a folder inside a Document Library in a SharePoint Team Site, the one that is provisioned when the Team was first created. In that Files tab, you are able to open that location by clicking "Open in... Continue Reading →
It is very easy to accidentally create an Office365 Group, for example by creating a new plan or creating new Team in Microsoft Teams; either of these (and I'm sure there are more ways) will provision an entire Office365 Group including mailbox, calendar, SharePoint team site and OneNote notebook. It doesn't create a team unless... Continue Reading →
When creating an Angular CLI app using the ng new command, the CLI itself will create some scripts in the packages.json relating to the building, testing, and local serving of your app. When running npm start it will subsequently run ng serve which by default runs the web server on localhost in HTTP (e.g. http://localhost:4200). This is all well and... Continue Reading →
UPDATE: Since this was written the office generator has been updated and does not work in the same way as below, specifically that it no longer asks to create a subfolder (for you to refuse) and does it anyway. If a folder already exists then it will fail and the instructions below are now useless.... Continue Reading →
