DLL Hell—a persistent challenge for .NET Framework developers—becomes particularly thorny when creating add-ins for complex applications like Revit. Juggling dependency versions often leads to cryptic conflicts, as each DLL expects a specific version...
sharpbim.hashnode.dev6 min read
Хорошо написал молодец 👌👉👌👅✌️
I would like to sincerely thank you Eng. Moustafa for this insightful solution to DLL conflict issues in Revit add-ins. Your work on utilizing AppDomain isolation to resolve DLL conflicts has been incredibly helpful. While I was initially struggling with similar issues, particularly with Material Design XAML in a WPF environment, I was able to solve the problem using Costura.Fody to embed referenced DLLs directly into the main DLL.
Your explanation provided me with a deeper understanding of the complexities of DLL management in Revit add-ins, and although I used a different approach, I deeply appreciate the clarity and thoughtfulness of your solution. I had previously tried multiple methods, including manual DLL injection, but they all fell short when dealing with WPF libraries. Costura.Fody was the breakthrough I needed to finally resolve these issues.
Thank you once again for sharing your knowledge and expertise with the community. Your contributions are highly valued, and I'm proud to have found such a useful resource. I will definitely recommend your solution to others facing similar challenges.
YZ777 Zhumabayev
BIM engineer and developer
Большое спасибо!