AuthorDaniel Marbach

Managing Application Secrets in Azure App Configuration Service with .NET Core Code Walkthrough

M

Introduction into managing Application Secrets in Azure App Configuration Service with .NET Core (previous)Managing Application Secrets in Azure App Configuration Service with .NET Core Code Walkthrough (current post) In the previous post I introduced various ways of storing secrets. In this post I’ll walk through the code required to pull out settings from User Secrets when running in development as well as from the Azure App Configuration Service when running in production. In order to...

Introduction into managing Application Secrets in Azure AppConfiguration Service with .NET Core

I

Introduction into managing Application Secrets in Azure App Configuration Service with .NET Core (current post)Managing Application Secrets in Azure App Configuration Service with .NET Core Code Walkthrough (next) Whether you are writing an ASP.NET Core website or a new .NET Core based application that will be run somewhere in the cloud you are almost always confronted with the question of where to reliably and securely store the application secrets. With the introduction of Microsoft...

Azure Service Bus Topology migration with NServiceBus

A

Azure Service Bus TopologiesAzure Service Bus Topologies with ForwardingAzure Service Bus Topologies of NServiceBusAzure Service Bus Topology migration with NServiceBus (current) In the last post I explained the complexity we introduced for our customers when we created multiple topologies without providing a smooth migration path. In this post I’ll walk you through the online migration path that we created to allow our customers to transition their existing NServiceBus endpoints using...

Azure Service Bus Topologies of NServiceBus

A

Azure Service Bus TopologiesAzure Service Bus Topologies with ForwardingAzure Service Bus Topologies of NServiceBus (current)Azure Service Bus Topology migration with NServiceBus (next) Almost a decade ago Particular Software started supporting customers running on Azure Service Bus by leveraging a robust and reliable queue abstraction called NServiceBus. Particular Software has been one of the early adopters of the PaaS Service. Hundreds of customers later we can look back at many scars and...

Azure Service Bus Topologies with Forwarding

A

In the previous blog post, I introduced topologies for Azure Service Bus and how topics and subscriptions can be leveraged to build reliable publish and subscribe infrastructure. All the approaches described in the last post have one major drawback: Subscriptions need to be managed for all events the subscriber wants to subscribe to. Wouldn't it be nice if we could automatically enqueue all messages in the input queue of the subscriber without having to manage receiving infrastructure for all...

Azure Service Bus Topologies

A

Once you start using Azure Service Bus, you are immediately confronted with queues, topics, subscriptions, and rules. Not only do you have to understand what operational capabilities each of those entities incorporate but you also have to come up with an optimal way of "stitching" them together to create a topology that will satisfy your needs. A good topology allows decoupling senders from receivers and publishers from subscribers by efficiently exchanging messages between clients connected to...

Integration Tests in Service Fabric – NUnitTestAssemblyRunner

I

In the previous post, I explained the inner workings of the communication listener and how it uses NUnitLite and a custom code to cache test names. In this post I’ll show how the NUnitTestAssemblyRunner is used to run individual tests when the client calls the Run method with individual test names. Without further ado The Run method executes the actual test run on a dedicated worker thread. With the setting of SynchronousEvents set to true introduced in the previous blog post, all event...

Integration Tests in Service Fabric – Communication Listener

I

In the previous post in my series on integration tests in Service Fabric I walked my readers through the AbstractTestRunner whose responsibility it is to discover tests in combination with the communication listener and exposes all the discovered tests to the client to be able to run individual tests over Service Fabric Remoting. In this post, I will introduce the communication listener which contains the actual test runner and discovery process which uses NUnit. Service Fabric SDK provides an...

Integration Tests in Service Fabric – Server side runner

I

In the last post in my series on integration tests in Service Fabric I showed how it is possible to use the C# API of the Service Fabric SDK to deploy the test applications dynamically to the cluster. The approach showed also used a ServiceProxy client that was able to interact with the server-side hosted inside the cluster over Service Fabric remoting. The service proxy is responsible for querying all tests that are hosted inside the test application and then instruct the service to run them...

Integration Tests in Service Fabric – Client side deployment

I

In the most recent post, I showed how the R base class fetches all the test definitions from the cluster and executes the tests one by one. In this post, I will walk you through the client side deployment. One of the nice benefits of Service Fabric is that it provides out of the box a relatively complete deployment story. It is possible to deploy application packages entirely in code by using Powershell or C#. All you need for that to work is the latest SDK. To deploy an application to the...

Recent Posts