[Azure] Local Service Fabric cluster won’t hit debug breakpoints

Today one in the “what the heck!?”-category. I had setup a freshly installed VM with Service Fabric SDK and Visual Studio, to debug a Service Fabric application. When I ran the app from VS, it got deployed into Service Fabric, all lights green. But weirdly, none of my breakpoints in Visual Studio were hit. So I tried numerous things like checking the debug profile in VS, rebuilding, removing the application, etc. etc. All to no avail.

When I tried resetting the cluster itself, I got the following error:

Access Control Lists are usually tied to folders, but of course this very helpful error does not include the actual folder. In the event log, a number of warnings were also feature, like:

Hmmm ok… again not that helpful. I’ll spare the Google query I’ve undertaken and skip to the end result:

Add the “ServiceFabricAdministrators” and “ServiceFabricUsers” groups to C:\SFDevCluster¬†with Full Control permissions. Those groups were not there in my case and once added, everything started behaving normally again. So not sure why they were not there, but adding them fixed everything. You’ll need to reset your cluster to get everything working afterwards.

[Azure] Deploying a Service Fabric cluster with custom SSL + client cert authentication

Within my current project we’re using Service Fabric in Azure to deploy a micro service (like) architecture. Upon a redesign of some parts of the solution, I decided to check whether I could improve our Service Fabric configuration. There were two things I wanted to achieve:

  1. Run the cluster on a custom URL, secured with a custom certificate.
  2. Use a client certificate for authentication of Azure DevOps deployments.

I’ll come to the why part of these requirements below.

Read More

[Azure] Removing Debugger NAT rules for service fabric load balancer

Sometimes your project forces you to do something you rather wouldn’t: debug in staging or production. Although you should definitely try to avoid these situations, sometimes sh*t just happens and that’s fine. If your project is running on Service Fabric, Azure offers you the option to attach a debugger right from within Visual Studio. This is a very powerful option which creates a connection between VS and your service fabric nodes in order to communicate with the remote debugger.¬† Read More