mirror of
https://github.com/aljazceru/btcpayserver.git
synced 2026-02-22 06:34:36 +01:00
e002f59f4c
Reported by @napoly In an integration test for a plugin, attempt to resolve a type provided by that plugin using `BTCPayServerTester`. For example: ``` tester.GetService<MoneroRPCProvider>(); ``` The type should be resolved successfully. The type fails to resolve. During the test run, the dotnet runtime attempts to load `MoneroRPCProvider` in the default load context (`AssemblyLoadContext.Default`). It locates the plugin assembly in the test directory and loads it there. In contrast, when BTCPay Server loads a plugin, it creates a dedicated plugin load context, and the plugin’s `MoneroRPCProvider` is loaded inside that context. This results in two distinct `MoneroRPCProvider` types: one in the default context and one in the plugin context. This PR forces the plugin context, during integration tests, to load the types it resolves into the default assembly context rather than its own. This prevents duplicate type definitions. As a side effect, behavior may differ slightly between running BTCPay Server normally and running tests, but this should be acceptable in most cases. Relevant discussion: #6851