My assumption is the same exact add-in works on your machine but not theirs. Correct? If not then you know that the add-in file is a renamed zip file so you can look in it in order to confirm that the assembly/DLL is present. Just copy to a file with the zip extension and open it using 7-Zip, WinZip, or a later Windows OS.Assuming that the DLL is present in the add-in:Perhaps your users have tighter security. What is their setting for BlockAddIns?http://help.arcgis.com/en/sdk/10.0/a...00004n7000000/It it possible that your add-in is referencing an assembly which is not present on the customers machine, e.g. maybe you are using the .NET 4.0 framework but they have not loaded it.It is possible that a virus scanner is blocking the assembly?Perhaps you could post your project with all the business logic removed?
Test addin on your office machines. The deployment is reported in Visual Studio's Output window when the project is built. The build's Output window reports information to diagnose the problem, if there are errors during the deployment process,.
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.