<?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 Re: VB6 App to esriAddIn: How to package custom OCXes in ArcObjects SDK Questions</title>
    <link>https://community.esri.com/t5/arcobjects-sdk-questions/vb6-app-to-esriaddin-how-to-package-custom-ocxes/m-p/756158#M20058</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;You also need to think about how you are going to handle uninstall.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 23 Dec 2010 11:55:35 GMT</pubDate>
    <dc:creator>RichardWatson</dc:creator>
    <dc:date>2010-12-23T11:55:35Z</dc:date>
    <item>
      <title>VB6 App to esriAddIn: How to package custom OCXes</title>
      <link>https://community.esri.com/t5/arcobjects-sdk-questions/vb6-app-to-esriaddin-how-to-package-custom-ocxes/m-p/756155#M20055</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello everyone:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have migrated a large VB6 ArcGIS 9.x application to VB.NET ArcGIS 10 add-in. It uses a couple of VB6 OCXes. Everything works fine on my development PC but when I start distributing the add-in, the target PC encounters COMexceptions. They go away if I register the OCXes manually on the target PC. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;What's the recommended 'best practice' methodology for distributing and, if necessary, registering the OCXes on target PCs when releasing ArcGIS Desktop extensions as add-ins?&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I think that I could create an installation package (with InstallShield for ex.) that would register the OCXes and automatically start the esriaddin file. It seems to defy the simplicity of end-users double-clicking on the esriaddin file. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Dec 2010 00:29:36 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcobjects-sdk-questions/vb6-app-to-esriaddin-how-to-package-custom-ocxes/m-p/756155#M20055</guid>
      <dc:creator>MeToo</dc:creator>
      <dc:date>2010-12-21T00:29:36Z</dc:date>
    </item>
    <item>
      <title>Re: VB6 App to esriAddIn: How to package custom OCXes</title>
      <link>https://community.esri.com/t5/arcobjects-sdk-questions/vb6-app-to-esriaddin-how-to-package-custom-ocxes/m-p/756156#M20056</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;If you use COM components then you have to register them because the registry is fundamental to how COM works.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;IMHO, the point of add-ins is to move away from COM thus enabling XCopy deployment.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;COM is incompatible with XCopy deployment.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Dec 2010 18:04:58 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcobjects-sdk-questions/vb6-app-to-esriaddin-how-to-package-custom-ocxes/m-p/756156#M20056</guid>
      <dc:creator>RichardWatson</dc:creator>
      <dc:date>2010-12-22T18:04:58Z</dc:date>
    </item>
    <item>
      <title>Re: VB6 App to esriAddIn: How to package custom OCXes</title>
      <link>https://community.esri.com/t5/arcobjects-sdk-questions/vb6-app-to-esriaddin-how-to-package-custom-ocxes/m-p/756157#M20057</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thanks Richard. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;What would prevent one from packaging the esriaddin and OCX/dependencies with InstallShield (for ex.), and having the latter "Start.exe theEsriAddIn" at the end of the installation? Would that work? The idea/hope would be that when the software is updated, the dependencies (that don't change) would already be on the end-user PCs and only the esriaddin would be needed and could be installed on a double-click.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I remember reading several months ago a couple of words (literally) in the esriaddin documentation that several libraries could be specified in the esriaddin Config.XML &amp;lt;Library=myProject.dll&amp;gt; tag. Could anybody give me an example of when that would be used?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Dec 2010 09:45:42 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcobjects-sdk-questions/vb6-app-to-esriaddin-how-to-package-custom-ocxes/m-p/756157#M20057</guid>
      <dc:creator>MeToo</dc:creator>
      <dc:date>2010-12-23T09:45:42Z</dc:date>
    </item>
    <item>
      <title>Re: VB6 App to esriAddIn: How to package custom OCXes</title>
      <link>https://community.esri.com/t5/arcobjects-sdk-questions/vb6-app-to-esriaddin-how-to-package-custom-ocxes/m-p/756158#M20058</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;You also need to think about how you are going to handle uninstall.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Dec 2010 11:55:35 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcobjects-sdk-questions/vb6-app-to-esriaddin-how-to-package-custom-ocxes/m-p/756158#M20058</guid>
      <dc:creator>RichardWatson</dc:creator>
      <dc:date>2010-12-23T11:55:35Z</dc:date>
    </item>
  </channel>
</rss>

