#SharePointProblems | Koskila.net

Solutions are worthless unless shared! Antti K. Koskela's Personal Professional Blog

Posts from December 2021

Blog posts published in December 2021

Posts from December 2021 (6)

  • Cover image for 2021 - Year Review!
    NEW
    Published on
    Authors
    koskila

    2021 - Year Review!

    Well, it's been a year. It certainly does not feel like it has been a whole 12 months since I last wrote one of these, you know? I failed every single one of the goals I set for 2021, but I'm not going to lie, family takes (and deserves) so much time that it is no wonder that our hobbies suffer a bit. But still - writing these year reviews has become a tradition, so without further ado - let's get to it! 😁 Website stats
  • Cover image for How to fix "Microsoft.WindowsAzure.Storage: Server encountered an internal error. Please try again after some time." when using IoTHub trigger for Azure Functions?
    Published on
    Authors
    koskila

    How to fix "Microsoft.WindowsAzure.Storage: Server encountered an internal error. Please try again after some time." when using IoTHub trigger for Azure Functions?

    One more article before Christmas! 😁 This time, I'll be fixing a function that's triggering based on new messages received through my IoT Hub in my Azure Functions project. Technically speaking, this is super simple to implement - your function needs to define an IoTHubTrigger , with an Event Hub name and usually a Connection String (I don't know why I'm Sentence Casing that, too, but I'll stick to it!
  • Cover image for How to authenticate against npm registries in Azure DevOps?
    Published on
    Authors
    koskila

    How to authenticate against npm registries in Azure DevOps?

    Another one in the series of "this should've been easy, but alas, you're the edge case". "You" being "me", and the "edge case" being our internal npm feed (registry), for whatever reason. Ah, well - life would be extremely boring if everything always went according to documentation, right? So, instead of the built-in ways to access npm feeds, this solution includes some PowerShell. Ah - that's when you know it's going to be good, right?
  • Cover image for How to test SignalR-connection in the browser?
    Published on
    Authors
    koskila

    How to test SignalR-connection in the browser?

    So a while back I posted about testing your "vanilla" WebSockets connection directly in the browser - and while that's nice and easy, sometimes you need to class up a bit. In my case that meant upgrading to SignalR (for some corporate and enterprisey reasons as usual). It makes sense to leave behind the easy, simple, lightweight and somewhat transparent WebSockets to "upgrade" to the enterprise-ready (and arguably quite a lot less transparent) SignalR?
  • Cover image for How to access claims of a SignalR user in ASP.NET Core?
    Published on
    Authors
    koskila

    How to access claims of a SignalR user in ASP.NET Core?

    I tend to post a lot of articles about different gotchas and configuration tweaks, but this one goes back to the roots a bit - just me and a couple of other devs hacking some code together and being blocked by a bit of an obstacle, that's then fixed by - you guessed it - writing niftier code. Or actually, I suppose it was more about removing some and adding some of the right stuff... But isn't that what most programming is about? Anyway - let's take a look at configuring SignalR for an ASP.
  • Cover image for Azure Function build fails with "Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: Microsoft.AspNetCore.Mvc.Core"
    Published on
    Authors
    koskila

    Azure Function build fails with "Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: Microsoft.AspNetCore.Mvc.Core"

    Another fun one with Azure Functions! At least it's a simple one: this time, I ran into a weird issue while doing some code reusing - well, copy-pasting - between a couple of different projects. I was lovingly hand-crafting some Azure Functions, while suddenly the Azure Functions host would throw this in ugly red letters: Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: 'Microsoft.AspNetCore.Mvc.Core, Version=3.1.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' at Mono.
Whitewater Magpie Ltd.
© 2026
Static Site Generation timestamp: 2026-02-03T09:01:56Z