Adding Files to esriAddinX

Question

I have a third party (licensing client) dll I need to include in my Add-In.  How do I make sure this file is included in my Add-Ins esriAddinX file?  It is not a .Net dll so I cannot easily include it as part of my Add-In solution.

JeffBoyton · Answer

I ended up using SetDllDirectory to augment the DLL search paths with the cache directory so that the existing DllImport directives would find the dll.  This worked just great.  Thanks for all of your help!

Wolf · Answer

Also some 3rd party libraries provide methods to change load location for any dlls or subprocesses. For example i wrote a sample using CefSharp which required this initialization code before i was able to use the control: if (!Cef.IsInitialized) { var settings = new CefSettings() { //By default CefSharp will use an in-memory cache, you need to specify a Cache Folder to persist data CachePath = System.IO.Path.Combine(Environment.GetFolderPath(Environment.SpecialFolder.LocalApplicationData), "CefSharp\Cache"), BrowserSubprocessPath = System.IO.Path.Combine(System.IO.Path.GetDirectoryName(System.IO.Path.GetFullPath(Assembly.GetExecutingAssembly().Location)), "CefSharp.BrowserSubprocess.exe") }; //Perform dependency check to make sure all relevant resources are in our output directory. Cef.Initialize(settings, performDependencyCheck: true, browserProcessHandler: null); }‍‍‍‍‍‍‍‍‍‍‍‍

Wolf · Answer

Add these lines in your Module class (this constructor should be called first) - rename Module1 to the name of your Module class: public Module1() { AppDomain currentDomain = AppDomain.CurrentDomain; currentDomain.AssemblyResolve += new ResolveEventHandler(ResolveProAssemblyPath); } ‍‍‍‍‍ And add this method to the module class: static System.Reflection.Assembly ResolveProAssemblyPath(object sender, ResolveEventArgs args) { string folderPath = System.IO.Path.GetDirectoryName(System.IO.Path.GetFullPath(System.Reflection.Assembly.GetExecutingAssembly().Location)); string assemblyPath = Path.Combine(folderPath, new System.Reflection.AssemblyName(args.Name).Name + ".dll"); if (!File.Exists(assemblyPath)) return null; System.Reflection.Assembly assembly = System.Reflection.Assembly.LoadFrom(assemblyPath); return assembly; }‍‍‍‍‍‍‍‍ Set a breakpoint in the static method to make sure it gets called before your dll is loaded and double check the path. Needless to say this all depends on the loading method that is used for your 3rd party dll and only works if the load failure event is triggered.