<?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: ArcGIS 10 and attribute edit screens in ArcObjects SDK Questions</title>
    <link>https://community.esri.com/t5/arcobjects-sdk-questions/arcgis-10-and-attribute-edit-screens/m-p/624763#M16808</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Melanie,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Have a look at &lt;/SPAN&gt;&lt;A href="http://help.arcgis.com/en/sdk/10.0/arcobjects_net/conceptualhelp/index.html#/Sample_Tabbed_feature_inspector/0001000004s8000000/"&gt;this&lt;/A&gt;&lt;SPAN&gt; example to start.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In short, Add-Ins aren't the answer in this case; the attribute editor is still referenced via COM, although it has .NET bindings that are used instead. An EXTCLSID is still required, but its mechanics may be different from your pre-existing solution. I'd have a look at the above referenced sample to see if your solution can be migrated, or if you're better of writing a new one from scratch.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 09 Mar 2011 18:26:20 GMT</pubDate>
    <dc:creator>JordanMacDonald</dc:creator>
    <dc:date>2011-03-09T18:26:20Z</dc:date>
    <item>
      <title>ArcGIS 10 and attribute edit screens</title>
      <link>https://community.esri.com/t5/arcobjects-sdk-questions/arcgis-10-and-attribute-edit-screens/m-p/624762#M16807</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;We have custom attribute edit screens written in VB6 for ArcMap 9.2 that use GDB_OBJECTCLASSES.EXTCLSID. When we copy the layer to ArcGIS 10 the custom screens come up nicely but of course don't work so I have a few questions. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Where is the EXTCLSID now stored in the new ArcGIS 10 geodatabase tables so I can remove the reference to old screens?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I know that in ArcGIS 10 the custom attribute edit screens will need to be re-written in .net but do they come in as COM component still or are they now supposed to be add-ins?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Mar 2011 18:15:31 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcobjects-sdk-questions/arcgis-10-and-attribute-edit-screens/m-p/624762#M16807</guid>
      <dc:creator>MelanieWawryk</dc:creator>
      <dc:date>2011-03-09T18:15:31Z</dc:date>
    </item>
    <item>
      <title>Re: ArcGIS 10 and attribute edit screens</title>
      <link>https://community.esri.com/t5/arcobjects-sdk-questions/arcgis-10-and-attribute-edit-screens/m-p/624763#M16808</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Melanie,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Have a look at &lt;/SPAN&gt;&lt;A href="http://help.arcgis.com/en/sdk/10.0/arcobjects_net/conceptualhelp/index.html#/Sample_Tabbed_feature_inspector/0001000004s8000000/"&gt;this&lt;/A&gt;&lt;SPAN&gt; example to start.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In short, Add-Ins aren't the answer in this case; the attribute editor is still referenced via COM, although it has .NET bindings that are used instead. An EXTCLSID is still required, but its mechanics may be different from your pre-existing solution. I'd have a look at the above referenced sample to see if your solution can be migrated, or if you're better of writing a new one from scratch.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Mar 2011 18:26:20 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcobjects-sdk-questions/arcgis-10-and-attribute-edit-screens/m-p/624763#M16808</guid>
      <dc:creator>JordanMacDonald</dc:creator>
      <dc:date>2011-03-09T18:26:20Z</dc:date>
    </item>
  </channel>
</rss>

