.NET Core fundamentals in one picture.

How to fix Microsoft.AspNetCore.Mvc.TagHelpers not being rendered!

Ha – another one, that ended up being a simple fix, but since nobody actually explains it well, took me an hour to figure out. This post ended up being another example of my “I’m going to document every single fix, that took me more than 10 minutes to figure out, since that’ll help me (and others) the next time the same issue arises.” blogging strategy. Snappy name, right? Never was my strongest suit! Anyway, I ended up banging my head to the wall. Hopefully…Continue reading How to fix Microsoft.AspNetCore.Mvc.TagHelpers not being rendered!

GitHub Desktop version information

Note to self: How to sync from the original repo on GitHub (Git merge upstream)

This is one of those “note to self” -kind of entries. This workflow is probably so natural to a lot of you all, that you won’t need to document it – but since I don’t do that much development with the full “fork – clone – branch – submit pull request” -process (whic is really typical with GitHub and I guess Open Source in general), I always need to look up the instructions on how to add pull any changes from the original repository to…Continue reading Note to self: How to sync from the original repo on GitHub (Git merge upstream)

Encountering AADSTS700054 in the wild. Always a bother - but let me tell you how to fix it!

How to fix “AADSTS700054: response_type ‘id_token’ is not enabled for the application” error

This article will explain to you how to fix the error “AADSTS700054” Another day, another unsuccessful authentication attempt, and another cool error code. This one I encountered when building a little POC that was supposed to authenticate against Graph API. Problem Table of Contents ProblemReasonSolution When developing your client-side solution (an SPFx webpart, React app, ASP.NET MVC application with some client-side components… Your pick!), you run into this error when your code tries to authenticate against Azure AD: AADSTS700054: response_type ‘id_token’ is not enabled for…Continue reading How to fix “AADSTS700054: response_type ‘id_token’ is not enabled for the application” error

Azure Active Directory, the advanced logo

How to fix “AADSTS500113: No reply address is registered for the application” error?

This article describes how to fix the error “AADSTS500113: no reply address is registered for the application”. You typically get this error, when your app is trying to authenticate your users against Azure Active Directory. I’ve been posting about different versions of Azure Active Directory authentication errors (different errors with AADSTS -codes) a lot – I’ll need to find a better way to categorize them in the future. But, for now, on to the issue! Problem Table of Contents ProblemSolution to error AADSTS500113 Another day,…Continue reading How to fix “AADSTS500113: No reply address is registered for the application” error?

Azure Functions CLI - such a pretty logo for such an awesome functionality

How to enable verbose logging for Azure Functions?

This post describes how you can easily enable debug/verbose information for your Azure Functions for a lightweight and built-in way to extract just a bit more information out of your Azure Function executions. There’s different methods available for Azure and your local development environment. Problem Table of Contents ProblemSolution Azure Functions are awesome. But by default, your tools on gathering information without some additional configuration are not that great. The “monitor” view of the function doesn’t give you more than an excerpt of the console.…Continue reading How to enable verbose logging for Azure Functions?

[SPLoaderError.loadComponentError]: ***Failed to load component "9951b316-c8f2-4e27-887a-b7a46b3e94a0" (ContosoSPFxWebPart). Original error: ***Failed to load path dependency "ContosoSPFxWebPartLocalization" from component "9951b316-c8f2-4e27-887a-b7a46b3e94a0" (ContosoSPFxWebPart). Original error: Error loading https://component-id.invalid/9951b316-c8f2-4e27-887a-b7a46b3e94a0_1.3.1/ContosoSPFxWebPartLocalization Unable to load script https://contoso.sharepoint.com/sites/contosoapps/ClientSideAssets/490f3be2-7e8a-4fe5-8d6b-49ae5d7c4a2e/s-ContosoSPFxWebPartLocalization_en-us_2b301efaa958eadafbad865f710d89e4.js ***INNERERROR: ***Failed to load path dependency "ContosoSPFxWebPartLocalization" from component "9951b316-c8f2-4e27-887a-b7a46b3e94a0" (ContosoSPFxWebPart). Original error: Error loading https://component-id.invalid/9951b316-c8f2-4e27-887a-b7a46b3e94a0_1.3.1/ContosoSPFxWebPartLocalization Unable to load script https://contoso.sharepoint.com/sites/contosoapps/ClientSideAssets/490f3be2-7e8a-4fe5-8d6b-49ae5d7c4a2e/s-ContosoSPFxWebPartLocalization_en-us_2b301efaa958eadafbad865f710d89e4.js ***CALLSTACK: Error at t [as constructor] (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-03-15.008/sp-pages-assembly_en-us_2676c0dcef2e33d08d5b8433ef878499.js:889:16049) at new t (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-03-15.008/sp-pages-assembly_en-us_2676c0dcef2e33d08d5b8433ef878499.js:1512:21125) at Function.e.buildErrorWithVerboseLog (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-03-15.008/sp-pages-assembly_en-us_2676c0dcef2e33d08d5b8433ef878499.js:1512:16214) at Function.e.buildLoadComponentError (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-03-15.008/sp-pages-assembly_en-us_2676c0dcef2e33d08d5b8433ef878499.js:1512:12245) at https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-03-15.008/sp-pages-assembly_en-us_2676c0dcef2e33d08d5b8433ef878499.js:1512:60385

SPFx webpart fails with “Failed to load component – – There was a network error.”

SPFx development is a bottomless bag of funsies! This article describes yet another way how to fix the error with your SPFx webpart failing to load a module. In this case, you’ll get an error that starts with the generic “Failed to load component” -part, but contains “There was a network error” later in the stack. I’ve written about this before, but I keep running into new ways to mess up, so I’ll keep documenting the solutions as well! Problem Table of Contents ProblemSolution So,…Continue reading SPFx webpart fails with “Failed to load component – – There was a network error.”

Koskela - SharePoint Saturday Nashville 2019 on 6/16 session.

Thanks for coming to my session at SPS Nashville 2019!

I had the honor of speaking at SharePoint Saturday Nashville 2019 again, and it was a lot of fun! I had the chance to meet a lot of new (and some “old”) people. And what a crowd – so many (difficult) questions about SPFx & Teams development… 😬😂 (Don’t want to crawl through the jabbering? Just here for the materials? Well, they are here: SPS Nashville 2019 materials . Thanks for your interest!) SPS Nashville 2019 from a speaker’s viewpoint Table of Contents SPS Nashville…Continue reading Thanks for coming to my session at SPS Nashville 2019!

Internet Explorer finally gets left behind

The boring version of browser wars is upon us

The next browser war is upon us, and this time it isn’t fought on the battlefield of proprietary API implementations and badly implemented CSS and JavaScript standards, but rather it’s different ecosystems battling it out with their respective variants of Blink, which itself is a part of open source Chromium. Sounds boring, right? And to some extent it really is. No Firefox fanboys, no Opera elitists and Internet explorer normies keeping to their respective corners of the public space, each group looking down on the…Continue reading The boring version of browser wars is upon us

Epic Visio Skills produced this cool illustration of Microsoft Teams extensibility!

Extending Microsoft Teams is now officially awesome

This article is something of a combination of a technology overview and an opinion piece, detailing my thoughts about extending Microsoft Teams. To me, extending Microsoft Teams has pretty much only now become relevant. Before, the palette was still quite unfinished, but now we’re definitely getting to a point where there are meaningful and cost-effective extension scenarios to cover most of the relevant use cases for most organizations. Don’t take this for an inflammatory or disrespectful post – I’m writing this from my personal point…Continue reading Extending Microsoft Teams is now officially awesome

Microsoft Teams extensibility

How to resolve “Error initializing application. Error: ***Manifest not found for component id [guid].” when adding an SPFx webpart to Teams?

This article describes one way to fix the issue, where uploading and sideloading an SPFx webpart in Microsoft Teams just brickwalls you with a fairly non-descriptive error, and no way to proceed. Luckily, this is usually simple to fix – I’ll describe 2 different solutions I’ve found so far! Problem Table of Contents ProblemSolutionsHow to verify you’re using the right guid for your Teams SPFx componentHow to enable sideloading SPFx webparts into TeamsHow to enable Microsoft Teams Developer preview?Additional information You’ve got a SPFx webpart,…Continue reading How to resolve “Error initializing application. Error: ***Manifest not found for component id [guid].” when adding an SPFx webpart to Teams?

Brave browser settings view

Enter the BRAVE new world of Chromium forks!

I’m trying out a new, more long-form content on this blog – tell me what you think about it in the comments section below! This article explains one of the only cryptocurrency initiatives I find to be kind of level-headed – Basic Attention Token – and the browser that’s pretty tightly coupled with it, Brave. Note: If you just want to skip all the banter and download the hecking browser, click this. Preface As far as different cryptocurrencies go, there have been quite a few…Continue reading Enter the BRAVE new world of Chromium forks!

[SPLoaderError.loadComponentError]: ***Failed to load component "9951b316-c8f2-4e27-887a-b7a46b3e94a0" (ContosoSPFxWebPart). Original error: ***Failed to load path dependency "ContosoSPFxWebPartLocalization" from component "9951b316-c8f2-4e27-887a-b7a46b3e94a0" (ContosoSPFxWebPart). Original error: Error loading https://component-id.invalid/9951b316-c8f2-4e27-887a-b7a46b3e94a0_1.3.1/ContosoSPFxWebPartLocalization Unable to load script https://contoso.sharepoint.com/sites/contosoapps/ClientSideAssets/490f3be2-7e8a-4fe5-8d6b-49ae5d7c4a2e/s-ContosoSPFxWebPartLocalization_en-us_2b301efaa958eadafbad865f710d89e4.js ***INNERERROR: ***Failed to load path dependency "ContosoSPFxWebPartLocalization" from component "9951b316-c8f2-4e27-887a-b7a46b3e94a0" (ContosoSPFxWebPart). Original error: Error loading https://component-id.invalid/9951b316-c8f2-4e27-887a-b7a46b3e94a0_1.3.1/ContosoSPFxWebPartLocalization Unable to load script https://contoso.sharepoint.com/sites/contosoapps/ClientSideAssets/490f3be2-7e8a-4fe5-8d6b-49ae5d7c4a2e/s-ContosoSPFxWebPartLocalization_en-us_2b301efaa958eadafbad865f710d89e4.js ***CALLSTACK: Error at t [as constructor] (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-03-15.008/sp-pages-assembly_en-us_2676c0dcef2e33d08d5b8433ef878499.js:889:16049) at new t (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-03-15.008/sp-pages-assembly_en-us_2676c0dcef2e33d08d5b8433ef878499.js:1512:21125) at Function.e.buildErrorWithVerboseLog (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-03-15.008/sp-pages-assembly_en-us_2676c0dcef2e33d08d5b8433ef878499.js:1512:16214) at Function.e.buildLoadComponentError (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-03-15.008/sp-pages-assembly_en-us_2676c0dcef2e33d08d5b8433ef878499.js:1512:12245) at https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-03-15.008/sp-pages-assembly_en-us_2676c0dcef2e33d08d5b8433ef878499.js:1512:60385

SPFx | Failed to load component.

This post describes the typical reasons why might encounter the following error, and the ways I’ve found to fix them: “Failed to load component. Original error: ***Failed to load path dependency ContosoSPFxWebPartLocalization from component [guid] (ContosoSPFxWebPart)” The error typically looks something like in the screenshot below: Problem This error can be thrown for a lot of different reasons. I’m trying to describe the variants I’ve run into and their fixes below. But first, let’s take a closer look into the error in question!

You cannot edit this page We're sorry, we encountered an unexpected error. Please try again, if the problem persists please contact your Administrator.

How to resolve “You cannot edit this page”-error in Modern SharePoint

This article describes an error situation that you might run into in Modern SharePoint, where you cannot take a page into edit mode anymore. You only get a strangely generic error message with a kinda weird failed request in the console. But, of course, there’s a fix – and an easy one at that! Problem Huh – so here’s a weird one for you! Take a modern communication site, create a new beautiful page, produce some high quality content, and even go to great extents…Continue reading How to resolve “You cannot edit this page”-error in Modern SharePoint

Koskela - SharePoint Saturday Nashville 2019 on 6/16 session.

Speaking at SPS Nashville 6/15/2019

Exciting news to share again! My session on using SPFx to extend Microsoft Teams got accepted to SharePoint Saturday Nashville next June. I’m excited to return to the Music City – it was a lot of fun last time, and I have a new session to present this time! Correction: The title has been fixed – it used to say 6/16, but the event is on 15. SharePoint Saturdays are typically on Saturday 😁 Thanks for pointing that out! What will I be speaking about?…Continue reading Speaking at SPS Nashville 6/15/2019

Let's fix SharePoint Search together!

How to add multiple aliases to a Managed Property in SharePoint Search?

This article explains how to add multiple aliases to one managed property in SharePoint Search Schema Management. Yes, it’s possible, just a bit unintuitive! I’ll explain the process below. Solution This seems to be another “gotcha”, that’s missing from the official documentation, but is super helpful to know when you happen to need it! The way I encountered it was in a dev/staging environment, where certain automatically created Managed Property, owstaxIdValoTags (I’ll leave it up to you to figure out what the name is all…Continue reading How to add multiple aliases to a Managed Property in SharePoint Search?

"Set-PnPAvailablePageLayouts -AllowAllPageLayouts" returning an error "Access denied. You do not have permission to perform this action or access this resource.."

How to fix “Access denied” errors when running “Set-PnPAvailablePageLayouts”?

This article describes one way how to fix seemingly non-sensical “Access denied” errors, that you get when running Set-PnPAvailablePageLayouts. Problem While running the PnP cmdlet for enabling or selecting the available publishing page layouts for a web, you run into this, fairly generic error: Access denied. You do not have permission to perform this action or access this resource. PS C:\> Set-PnPAvailablePageLayouts -AllowAllPageLayouts Set-PnPAvailablePageLayouts : Access denied. You do not have permission to perform this action or access this resource. At line:1 char:1 + Set-PnPAvailablePageLayouts…Continue reading How to fix “Access denied” errors when running “Set-PnPAvailablePageLayouts”?

Azure Functions CLI - such a pretty logo for such an awesome functionality

How to access EF’s DbContext in an Azure Function on V2 runtime?

This post describes how you can access your Entity Framework Core model classes and the database context in your Azure Functions. In my example I’m using EF Core 2.1, but the main principle should be the same for later versions as well. Please note, that I use Azure functions runtime 2.x (and so should you!) Another easy one, that I was unable to find much guidance on! But first, let’s start with the basics. Why would you want to have this setup? Why would you…Continue reading How to access EF’s DbContext in an Azure Function on V2 runtime?

SharePoint PnP logo

Another fix to “Connect-PnPOnline : The sign-in name or password does not match one in the Microsoft account system.”

This post describes a simple way to get around the following error while running Connect-PnPOnline: “The sign-in name or password does not match one in the Microsoft account system.” Truthfully, this one is kind of simple and stupid – but as I’ve seen before, it’s surely worth documenting anyway! Below is an example of such error. PS C:\> Connect-PnPOnline https://contoso.sharepoint.com/sites/CommunicationSite/ Connect-PnPOnline : The sign-in name or password does not match one in the Microsoft account system. At line:1 char:1 + Connect-PnPOnline https://contoso.sharepoint.com/sites/CommunicationS … + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~…Continue reading Another fix to “Connect-PnPOnline : The sign-in name or password does not match one in the Microsoft account system.”

Azure Functions CLI - such a pretty logo for such an awesome functionality

Sudden “Function compilation error” for an Azure Function

Welp – another interesting error encountered while deploying Azure Functions to Azure. So, everything runs nicely locally, but when you deploy your well-tested, functional and pretty code to run them in the cloud, you’ll just get these ugly and unfriendly errors. Long story short, “Function compilation error” is what you’re faced with. Example error below: Function compilation error Microsoft.CodeAnalysis.Scripting.CompilationErrorException : Script compilation failed. at async Microsoft.Azure.WebJobs.Script.Description.DotNetFunctionInvoker.CreateFunctionTarget(CancellationToken cancellationToken) at C:\azure-webjobs-sdk-script\src\WebJobs.Script\Description\DotNet\DotNetFunctionInvoker.cs : 314 at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at async Microsoft.Azure.WebJobs.Script.Description.FunctionLoader`1.GetFunctionTargetAsync[T](Int32 attemptCount) at C:\azure-webjobs-sdk-script\src\WebJobs.Script\Description\FunctionLoader.cs : 55 at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at async…Continue reading Sudden “Function compilation error” for an Azure Function