Use AssemblyLoadContext Internally Within Vault Add-Ins With Vault 2026+ using .NET 8 (& the separated .NET Core version of 2025), there is no separate execution context for the add-in to run. So, if there is a NuGet package/assembly version conflict with the add-in and Vault or another add-in, it will cause an error. Below are some resources for how to do this manually within each add-in. Could this be built into the standard 'IWebServiceExtension', 'IExplorerExtension', & 'IJobHandler' to prevent the need to do this manually? Blog article on Vault add-in implementing AssemblyLoadContext: https://tylerwarner.dev/assemblyloadcontext-for-vault-addins Sample Vault add-in implementing AssemblyLoadContext: https://github.com/tylerwarner33/autodesk-vault-assembly-load-context Blog article on Vault add-in implementing AssemblyLoadContext via a NuGet that updates the IL code at runtime: https://tylerwarner.dev/assemblyloadcontext-for-autodesk-addins-with-isolatorfody Sample Vault add-in implementing AssemblyLoadContext via a NuGet that updates the IL code at runtime: https://github.com/tylerwarner33/autodesk-vault-assembly-load-context-fody Revit implementation discussion about internal implementation: https://feedback.autodesk.com/project/forum/thread.html?cap=cb0fd5af18bb49b791dfa3f5efc47a72&forid=%... Accepted Inventor idea for the same internal implementation: https://forums.autodesk.com/t5/inventor-ideas/use-assemblyloadcontext-internally-within-inventor-add-ins/idc-p/14004748#M52374
Show More