Re: How to best handle dll conflicts with revit addins

Sorry the video was this one RevitLookup - End of DLL hell - Revit API. I'm not sure if the intention was to show loading multiple different contexts, but at the end of the video you should how adding a static class with static property is updated separately from either button. The issue here is that each button seems to effectively have its own context. I would find this behaviour odd as a developer and can be resolved by simply having a single context. When I tested out this approach, I needed a single context which avoids the same dll being spread across multiple contexts. Again I still think this is a much better approach t IL-repack as there is no real downsides, unlike IL-repack which comes with build times and caution about using versions of framework references that aren't compatible between projects.

As for hot reload I find it works really well, at least I have not run into any issues yet.

And finally, yes I agree, it would have been much more ideal if Revit were loading the addins in a separate context as this would avoid a lot of headache for developers, and in my opinion should have been done as part of the .net core support being added.