Repository navigation
Keep UI benchmark dependencies in the same load context #68
Description
Description of the new feature / enhancement
UI benchmarks load their client assemblies and dependencies in the same context.
Revit API and runtime contracts remain shared.
Scenario when this would be used?
A RevitApiUiBenchmark project targets Revit 2025 on .NET 8 and ships a newer runtime library.
Revit has already loaded a client assembly of the same version.
Separate contexts can resolve different dependency types in public method signatures.
Activity
[-]Isolate UI benchmark client dependencies with Injector patch 13[/-][+]Keep UI benchmark dependencies in the same load context[/+]