<?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: Deploying EsriAddIns using ClickOnce Technology in ArcObjects SDK Questions</title>
    <link>https://community.esri.com/t5/arcobjects-sdk-questions/deploying-esriaddins-using-clickonce-technology/m-p/168535#M4351</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;If you have to register that dll then it is required that the user running the registration have read/write permissions on the system registry.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 01 Aug 2011 12:54:18 GMT</pubDate>
    <dc:creator>NeilClemmons</dc:creator>
    <dc:date>2011-08-01T12:54:18Z</dc:date>
    <item>
      <title>Deploying EsriAddIns using ClickOnce Technology</title>
      <link>https://community.esri.com/t5/arcobjects-sdk-questions/deploying-esriaddins-using-clickonce-technology/m-p/168534#M4350</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 developed an EsriAddIn extension/toolbar that relies on a third-party dll that I also supply. Because of the dll, I have been deploying the application using the InstallShield Limited Edition available in/for Visual Studio 2010 (VS). It works fine. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;However, I am frustrated by my customers needing administrative rights to install the dll and their keycodes (custom built and placed in C:\ProgramData as recommended, I think, by Microsoft). In addition, it's a challenge to keep all users up to date with the latest version. EsriAddIns don't require administrative rights. FYI, mine is also signed.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The dll doesn't need to be updated after initial installation, but the EsriAddIn and keycodes (plain txt files) do.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So, I am considering the VS ClickOnce technology. Can this be done? Is that going to help with the need for admin rights? Comments, pros &amp;amp; cons, particularly regarding the above scenario?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Dennis&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Two side-questions: &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;1- Is their a way to use a dll from an EsriAddIn without having to register the dll in Windows first? That would fix half of my problems.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;2- Any way of preventing security suites like Norton from seeing an esriaddin as a zip file? This prevents a user from being able to install the add-in by clicking on it on a web page as it associates an "unzip action" to it and not "esriaddin action". It also prevents the "ClickOnce" technology built in EsriAddIns from working.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 30 Jul 2011 02:20:41 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcobjects-sdk-questions/deploying-esriaddins-using-clickonce-technology/m-p/168534#M4350</guid>
      <dc:creator>MeToo</dc:creator>
      <dc:date>2011-07-30T02:20:41Z</dc:date>
    </item>
    <item>
      <title>Re: Deploying EsriAddIns using ClickOnce Technology</title>
      <link>https://community.esri.com/t5/arcobjects-sdk-questions/deploying-esriaddins-using-clickonce-technology/m-p/168535#M4351</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;If you have to register that dll then it is required that the user running the registration have read/write permissions on the system registry.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Aug 2011 12:54:18 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcobjects-sdk-questions/deploying-esriaddins-using-clickonce-technology/m-p/168535#M4351</guid>
      <dc:creator>NeilClemmons</dc:creator>
      <dc:date>2011-08-01T12:54:18Z</dc:date>
    </item>
    <item>
      <title>Re: Deploying EsriAddIns using ClickOnce Technology</title>
      <link>https://community.esri.com/t5/arcobjects-sdk-questions/deploying-esriaddins-using-clickonce-technology/m-p/168536#M4352</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thanks Neil:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Are there any cases where a dll doesn't need to be registered?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks again,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Dennis&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Aug 2011 13:08:02 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcobjects-sdk-questions/deploying-esriaddins-using-clickonce-technology/m-p/168536#M4352</guid>
      <dc:creator>MeToo</dc:creator>
      <dc:date>2011-08-01T13:08:02Z</dc:date>
    </item>
    <item>
      <title>Re: Deploying EsriAddIns using ClickOnce Technology</title>
      <link>https://community.esri.com/t5/arcobjects-sdk-questions/deploying-esriaddins-using-clickonce-technology/m-p/168537#M4353</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;It depends on what type of dll it is.&amp;nbsp; For instance, a .NET assembly dll doesn't require registration if you install it alongside the assemblies that reference it.&amp;nbsp; On the other hand, ActiveX dlls usually require registration and typically will not work if you simply install them alongside your application assemblies.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Aug 2011 13:23:43 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcobjects-sdk-questions/deploying-esriaddins-using-clickonce-technology/m-p/168537#M4353</guid>
      <dc:creator>NeilClemmons</dc:creator>
      <dc:date>2011-08-01T13:23:43Z</dc:date>
    </item>
  </channel>
</rss>

