I recently embarked on a journey with my colleague Lukman Balunywa to uncover all the details involved in connecting a custom Power Apps connector to an Azure APIM instance. This blog post is the result of this research which will help you navigate some of the pitfalls you may face while attempting to connect these two services together.
Before we start discussing the details behind the integration between the two services it’s important to start by understanding the APIM environment that is being exposed. The APIM instance exposes a logic app backend. The API on the APIM frontend is protected…
This is part 2 of a 2 part series where we discuss automating the deployment of an APIM changes as well as automating the Logic Apps deployment which are utilized as backends for the APIM instance.
Part 2 — Automating Deployment of Azure Logic App Using Azure DevOps
In part 1 we discussed in details how to automate deployment of Azure API Management APIs and their configurations from one environment to another. In this post we switch our focus to building CI/CD pipelines for the Logic Apps…
This is part 1 of a 2 part series where we discuss automating the deployment of an APIM changes as well as automating the Logic Apps deployment which are utilized as backends for the APIM instance.
Part 1 — Automating Deployment of Azure API Management Changes Using Azure DevOps
With the strategic value of APIs, a continuous integration (CI) and continuous deployment (CD) pipeline has become an important aspect of API development. …
I recently embarked on a mission to uncover the details behind the implementation of MicroFrontends under Blazor WebAssembly applications. This post represents a summary of my findings along with a sample application that should serve as a good starting point as you start your own journey of introducing MicroFrontends to your Blazor WebAssembly project.
An excellent place to start understanding MicroFrontends is the following session from .Net Conf 2020 by Florian Rappl. In the session Florian goes through the different options available to introduce MicroFrontends to a Blazor WebAssembly application. I won’t go again over the problem statement of Monolithic…
I recently embarked on a mission with my colleague Marius Rochon to secure a Blazor WebAssembly application using Azure AD. The application utilizes a backend API which is also secured using Azure AD. Whereas Azure AD makes the process a breeze to setup, experience has taught us that the devil lies in the details. This post chronicles our journey to secure a Blazor WebAssembly application.
The source code is hosted on my GitHub repository which can be found here.
The solution includes two projects. The Blazor WebAssembly project and a WebAPI project.
Its no secret by now that there has been a lot of excitement about gRPC recently in the .Net community. gRPC is a modern high-performance RPC (Remote Procedure Call) framework. It is based on HTTP/2, Protocol Buffers and other modern standard-based technologies. It is also an open standard and is supported by many programming languages, including .NET.
It is currently impossible to implement the gRPC HTTP/2 spec in the browser because there are no browser APIs with enough fine-grained control over requests. Well the good news is that gRPC-Web is here for the rescue!!!
gRPC-Web is a standardized protocol that…
I recently ran into an issue where running a Blazor WebAssembly application under unsupported browsers would simply get stuck on the loading page. Whereas older browsers are supported under the “Server Side” model, it would be a much better experience to present the user with a more meaningful indicator that the browser is not supported when running “Blazor WebAssembly” model. Currently, when running Blazor WebAssembly under older browsers you get a loading indicator that never materializes to a page.
In an era where Continuous Integration/Continuous Deployment (CI/CD) is the norm, improving build times becomes a necessity for a successful DevOps strategy. One of the essential factors that lead to improved build times is eliminating the waste. When building an Angular application this means avoiding downloading the same npm packages after each build. Not only is it a time consuming process but it also introduces several unnecessary API calls.
Blazor offers many benefits to .Net developers ranging from providing a Single Page Application (SPA) framework option, to features like two-way binding and offline support just to name a few. But one of the main benefits that has been resonating with a lot of .Net developers is the fact that it’s component based. Whereas its highly recommended to start with a Blazor application whenever possible, it’s also plausible to consider integrating Blazor components into existing ASP.Net Core MVC applications(or Razor pages for that matter). The aforementioned scenario comes up in one of two cases:
Its not a secret by now that Blazor is taking the .Net Core world by storm. I won’t go into the details of what Blazor is or how the different hosting models work as its been widely discussed in the community. For a quick reference of Blazor overview as well as the different hosting models you can check the Microsoft docs located here and here, respectively. In this post I will mainly focus on hosting a containerized WebAssembly Blazor application on Azure. I will use Azure DevOps to build a CI/CD pipeline which will deploy the Docker image that contains…
Senior Cloud Solution Architect @Microsoft. I am a Web Enthusiast. Oh and Public Speaking is kind of my thing. #Microsoft, #emp, #Msftemployee,