<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Shared Add-Ins Not Updating - Possible Cause in ArcObjects SDK Questions</title>
    <link>https://community.esri.com/t5/arcobjects-sdk-questions/shared-add-ins-not-updating-possible-cause/m-p/453071#M12301</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;An "undocumented feature" of ArcGIS I have found dealing with shared add-ins can give you the impression updating from the shared folder is not working. One cause of this is older versions of the add-in in sub-folders of the shared folder.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Example scenario:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- Add-in "myArcMapTools.esriAddIn" stored in a shared folder "G:\ESRI\SharedAddins\"&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- When updating the add-in, you archive the old add-ins to a sub-folder of this folder so that you can revert back to an old copy&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- ie. Backup add-in "myArcMapTools.esriAddIn.bak" stored in sub-folder "G:\ESRI\SharedAddins\Archive\"&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;When ArcGIS opens, it not only searches the shared folder, but sub-folders of that shared folder, and also locates any add-in files regardless if whether the file extension is ".esriAddIn" or not. ArcGIS will install the add-in (with the same CLSID) with the oldest created date, thus in the above scenario, the backup add-in will be installed, and not the updated add-in.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;This is possibly expected behavior, but it is undocumented. It is also possible that the search for add-ins is recursive and thus if you have your add-in in the root of a shared drive, ArcGIS will search all folders and sub-folders within that drive for add-ins (which may produce performance issues and undesirable results.)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The fix/workaround for the above scenario is to not have the backup versions in a sub-folder, but in a different folder altogether&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- Add-in "myArcMapTools.esriAddIn" stored in a shared folder "G:\ESRI\SharedAddins\"&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- Backup add-in "myArcMapTools.esriAddIn.bak" stored in folder "G:\ESRI\ArchivedAddins\"&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 30 Jun 2014 07:55:29 GMT</pubDate>
    <dc:creator>DonOBrien</dc:creator>
    <dc:date>2014-06-30T07:55:29Z</dc:date>
    <item>
      <title>Shared Add-Ins Not Updating - Possible Cause</title>
      <link>https://community.esri.com/t5/arcobjects-sdk-questions/shared-add-ins-not-updating-possible-cause/m-p/453071#M12301</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;An "undocumented feature" of ArcGIS I have found dealing with shared add-ins can give you the impression updating from the shared folder is not working. One cause of this is older versions of the add-in in sub-folders of the shared folder.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Example scenario:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- Add-in "myArcMapTools.esriAddIn" stored in a shared folder "G:\ESRI\SharedAddins\"&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- When updating the add-in, you archive the old add-ins to a sub-folder of this folder so that you can revert back to an old copy&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- ie. Backup add-in "myArcMapTools.esriAddIn.bak" stored in sub-folder "G:\ESRI\SharedAddins\Archive\"&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;When ArcGIS opens, it not only searches the shared folder, but sub-folders of that shared folder, and also locates any add-in files regardless if whether the file extension is ".esriAddIn" or not. ArcGIS will install the add-in (with the same CLSID) with the oldest created date, thus in the above scenario, the backup add-in will be installed, and not the updated add-in.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;This is possibly expected behavior, but it is undocumented. It is also possible that the search for add-ins is recursive and thus if you have your add-in in the root of a shared drive, ArcGIS will search all folders and sub-folders within that drive for add-ins (which may produce performance issues and undesirable results.)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The fix/workaround for the above scenario is to not have the backup versions in a sub-folder, but in a different folder altogether&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- Add-in "myArcMapTools.esriAddIn" stored in a shared folder "G:\ESRI\SharedAddins\"&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- Backup add-in "myArcMapTools.esriAddIn.bak" stored in folder "G:\ESRI\ArchivedAddins\"&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Jun 2014 07:55:29 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcobjects-sdk-questions/shared-add-ins-not-updating-possible-cause/m-p/453071#M12301</guid>
      <dc:creator>DonOBrien</dc:creator>
      <dc:date>2014-06-30T07:55:29Z</dc:date>
    </item>
    <item>
      <title>Re: Shared Add-Ins Not Updating - Possible Cause</title>
      <link>https://community.esri.com/t5/arcobjects-sdk-questions/shared-add-ins-not-updating-possible-cause/m-p/453072#M12302</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;BR /&gt;ArcGIS honors the Addin that was most recently added to the Well-Known folder, even if it is more outdated than the current Add-in.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I tested the below workflow on ArcGIS 10.3.1 to reach the above conclusion.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1- Create an Addin called ArcMapAddin1 in Visual Studio, and create a button that pops up a message box that reads &lt;STRONG&gt;"This is Addin1 before an update".&lt;/STRONG&gt; Build your Visual Studio project so as to output the *.esriaddin file.&lt;/P&gt;&lt;P&gt;2- Copy the ArcMapAddin1.esriaddinx file from the bin folder to a &lt;STRONG&gt;well-known folder&lt;/STRONG&gt;, e.g. C:\Temp&lt;/P&gt;&lt;P&gt;3- Run ArcMap.&lt;/P&gt;&lt;P&gt;4- ArcMap's &lt;STRONG&gt;Addin Manager&lt;/STRONG&gt; shows that a "shared-Addin" called Addin1 has been recently installed.&lt;/P&gt;&lt;P&gt;5- From the &lt;STRONG&gt;Customize&lt;/STRONG&gt; menu, drag the Addin1 button to a toolbar, and click it.&lt;/P&gt;&lt;P&gt;6- A message box is displayed; as expected, it reads&lt;STRONG&gt; "This is Addin1 before an update"&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;7- Close ArcMap.&lt;/P&gt;&lt;P&gt;8 - Make a small change to the Addin1 in Visual Studio. Change the Message Box to read &lt;STRONG&gt;"This is an UPDATED Addin1"&lt;/STRONG&gt;. Clean and rebuild your project so as to output an updated *.esriaddin file in the bin folder of your project.&lt;/P&gt;&lt;P&gt;9 - Copy the updated *.esriaddin file from the bin folder over to a new folder one level below your &lt;STRONG&gt;Well-Known Folder, &lt;/STRONG&gt;for example, C:\Temp\Update.&lt;/P&gt;&lt;P&gt;10- Open ArcMap and click the Addin1 button on the toolbar.&lt;/P&gt;&lt;P&gt;11- You should see a message box that reads&lt;STRONG&gt; "This is an UPDATED Addin1".&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;12- Copy both Addins from the Well-Known folder to a temporary location, e.g. C:\Temp2\Addin1 and C:\Temp2\Addin1\Update.&lt;/P&gt;&lt;P&gt;13- Delete the two Addins from the Well-Known folder&lt;/P&gt;&lt;P&gt;14- Then, copy the Addin in C:\Temp2\Addin1\Update to C:\Temp. This is the most recently created Addin.&lt;/P&gt;&lt;P&gt;15- Run ArcMap and click on the button. You will get the message &lt;STRONG&gt;"This is an UPDATED Addin1".&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;16- Now, Copy the Addin in C:\Temp2\Addin1 to C:\Temp\Update. This is the more outdated Addin.&lt;/P&gt;&lt;P&gt;17 - Run ArcMap and click on the button. You will get the message &lt;STRONG&gt;"This is Addin1 before an update"&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;18- Thus, ArcMap honors the Addin that was most recently copied to the Well-Known Folder, regardless of whether it is more outdated than the existing one. It does not honor the date of creation of the Add-in.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 28 Sep 2015 23:22:45 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcobjects-sdk-questions/shared-add-ins-not-updating-possible-cause/m-p/453072#M12302</guid>
      <dc:creator>seria</dc:creator>
      <dc:date>2015-09-28T23:22:45Z</dc:date>
    </item>
  </channel>
</rss>

