Do we even need IMainDom?

[JasonElkin]

In replying to this thread about yet another locking issue with the FileSystemMainDomLock, I got to thinking…

MainDom Lock Timeout on Azure App Service - Looking for Solution

Environment: Umbraco CMS 15.4.3 .NET 9 on Windows (Azure App Service) Azure App Service: 2 separate App Service Plans Backoffice: SchedulingPublisher (minimal traffic) Public: Subscriber (~100k requests/day, traffic doubled recently) One instance each, no scaling out Configuration: FileSystemMainDomLock with LocalTempStorageLocation = EnvironmentTemp Problem: Subscriber server crashes on restart when under load with: System.TimeoutException: Cannot acquire MainDom at …

What does IMainDom actually do? Looking at the file itself…

There can be only one “main” AppDomain running for a given application at a time.

Quite right too! But in .NET Core you can’t have multiple AppDomains running at the same time….

Can we just nuke this whole concept and save everyone a lot of time and tears?