<?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: Replacement for extending AddIns.Extension in ArcGIS Pro SDK Questions</title>
    <link>https://community.esri.com/t5/arcgis-pro-sdk-questions/replacement-for-extending-addins-extension/m-p/785534#M1246</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Lesley&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The recommended way to store properties to be used across an add-in is to use the Module class file.&lt;/P&gt;&lt;P&gt;In an add-in, you will have a Module1.cs class file. For convenience,&amp;nbsp; the "Current" property is created in the add-in when you use the Pro SDK Templates to create an add-in. Instance properties in the Module1 class can be accessed across the add-in as Module1.Current.&amp;lt;PropertyName&amp;gt;.&amp;nbsp; Static properties can be accessed directly using Module1.&amp;lt;StaticProperty&amp;gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You will see this pattern in many of the samples in the &lt;A href="https://github.com/Esri/arcgis-pro-sdk-community-samples"&gt;arcgis-pro-community-samples repository&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Uma&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 04 Dec 2019 23:53:44 GMT</pubDate>
    <dc:creator>UmaHarano</dc:creator>
    <dc:date>2019-12-04T23:53:44Z</dc:date>
    <item>
      <title>Replacement for extending AddIns.Extension</title>
      <link>https://community.esri.com/t5/arcgis-pro-sdk-questions/replacement-for-extending-addins-extension/m-p/785533#M1245</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;With ArcMap AddIns, I extended the AddIns.Extension class to create a custom extension as a central repository to store states and variables that were relevant to different workflows in my AddIn. For example: the currently selected area of interest. To access the custom extension from any workflow in the AddIn, I used the&amp;nbsp;Application.FindExtensionByCLSID() method. Is there a recommended design pattern for centrally storing this type of information in ArcGIS Pro?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;P&gt;Friend Shared Function GetExtension() As BagisPExtension&lt;BR /&gt;&amp;nbsp; ' Extension loads just in time, call FindExtension to load it.&lt;BR /&gt;&amp;nbsp; If s_extension Is Nothing Then&lt;BR /&gt;&amp;nbsp; &amp;nbsp; Dim extID As UID = New UID()&lt;BR /&gt;&amp;nbsp; &amp;nbsp; extID.Value = My.AddInID&lt;BR /&gt;&amp;nbsp; &amp;nbsp; My.ArcMap.Application.FindExtensionByCLSID(extID)&lt;BR /&gt;&amp;nbsp; End If&lt;BR /&gt; Return s_extension&lt;BR /&gt; End Function&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Nov 2019 23:33:10 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-sdk-questions/replacement-for-extending-addins-extension/m-p/785533#M1245</guid>
      <dc:creator>LesleyBross1</dc:creator>
      <dc:date>2019-11-22T23:33:10Z</dc:date>
    </item>
    <item>
      <title>Re: Replacement for extending AddIns.Extension</title>
      <link>https://community.esri.com/t5/arcgis-pro-sdk-questions/replacement-for-extending-addins-extension/m-p/785534#M1246</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Lesley&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The recommended way to store properties to be used across an add-in is to use the Module class file.&lt;/P&gt;&lt;P&gt;In an add-in, you will have a Module1.cs class file. For convenience,&amp;nbsp; the "Current" property is created in the add-in when you use the Pro SDK Templates to create an add-in. Instance properties in the Module1 class can be accessed across the add-in as Module1.Current.&amp;lt;PropertyName&amp;gt;.&amp;nbsp; Static properties can be accessed directly using Module1.&amp;lt;StaticProperty&amp;gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You will see this pattern in many of the samples in the &lt;A href="https://github.com/Esri/arcgis-pro-sdk-community-samples"&gt;arcgis-pro-community-samples repository&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Uma&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Dec 2019 23:53:44 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-sdk-questions/replacement-for-extending-addins-extension/m-p/785534#M1246</guid>
      <dc:creator>UmaHarano</dc:creator>
      <dc:date>2019-12-04T23:53:44Z</dc:date>
    </item>
    <item>
      <title>Re: Replacement for extending AddIns.Extension</title>
      <link>https://community.esri.com/t5/arcgis-pro-sdk-questions/replacement-for-extending-addins-extension/m-p/785535#M1247</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Uma ~&lt;/P&gt;&lt;P&gt;That works! For others trying to do something similar, the&amp;nbsp;ArcGISOnlineConnect project in the samples was the closest to what I was trying to do.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Dec 2019 21:30:12 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-sdk-questions/replacement-for-extending-addins-extension/m-p/785535#M1247</guid>
      <dc:creator>LesleyBross1</dc:creator>
      <dc:date>2019-12-06T21:30:12Z</dc:date>
    </item>
  </channel>
</rss>

