<?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: IFeatureLayer vs IFeatureLayer2 in ArcObjects SDK Questions</title>
    <link>https://community.esri.com/t5/arcobjects-sdk-questions/ifeaturelayer-vs-ifeaturelayer2/m-p/703526#M18844</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Deprecating interfaces breaks the COM contract so it will probably be there for the foreseeable future.&amp;nbsp; The only time I saw esri deprecate interfaces is when they deprecated the class too.&amp;nbsp; if you look at the classes that implement IFeatureLayer2 and compare to the classes that implement IFeatureLayer, you will notice not all classes the implement IFeatureLayer, implement IFeatureLayer2, so for those you have no choice.&amp;nbsp; ArcObjects is littered with 2, 3, 4... interfaces for the precise reason that COM forbids modifying a published interface so if you have a compelling reason to use IFeatureLayer (maybe the method you want to use returns IFeatureLayer or takes it in,) then you are fine.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 22 Oct 2012 14:25:56 GMT</pubDate>
    <dc:creator>AlexanderGray</dc:creator>
    <dc:date>2012-10-22T14:25:56Z</dc:date>
    <item>
      <title>IFeatureLayer vs IFeatureLayer2</title>
      <link>https://community.esri.com/t5/arcobjects-sdk-questions/ifeaturelayer-vs-ifeaturelayer2/m-p/703525#M18843</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;The help mentions that IFeatureLayer2 supersedes IFeatureLayer. Does that mean eventually IFeatureLayer will be deprecated? Or is it OK to continue using IFeatureLayer even for new work and only IFeatureLayer2 if I need its extra methods?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Oct 2012 14:05:04 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcobjects-sdk-questions/ifeaturelayer-vs-ifeaturelayer2/m-p/703525#M18843</guid>
      <dc:creator>WayneGuidry</dc:creator>
      <dc:date>2012-10-22T14:05:04Z</dc:date>
    </item>
    <item>
      <title>Re: IFeatureLayer vs IFeatureLayer2</title>
      <link>https://community.esri.com/t5/arcobjects-sdk-questions/ifeaturelayer-vs-ifeaturelayer2/m-p/703526#M18844</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Deprecating interfaces breaks the COM contract so it will probably be there for the foreseeable future.&amp;nbsp; The only time I saw esri deprecate interfaces is when they deprecated the class too.&amp;nbsp; if you look at the classes that implement IFeatureLayer2 and compare to the classes that implement IFeatureLayer, you will notice not all classes the implement IFeatureLayer, implement IFeatureLayer2, so for those you have no choice.&amp;nbsp; ArcObjects is littered with 2, 3, 4... interfaces for the precise reason that COM forbids modifying a published interface so if you have a compelling reason to use IFeatureLayer (maybe the method you want to use returns IFeatureLayer or takes it in,) then you are fine.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Oct 2012 14:25:56 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcobjects-sdk-questions/ifeaturelayer-vs-ifeaturelayer2/m-p/703526#M18844</guid>
      <dc:creator>AlexanderGray</dc:creator>
      <dc:date>2012-10-22T14:25:56Z</dc:date>
    </item>
    <item>
      <title>Re: IFeatureLayer vs IFeatureLayer2</title>
      <link>https://community.esri.com/t5/arcobjects-sdk-questions/ifeaturelayer-vs-ifeaturelayer2/m-p/703527#M18845</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;Deprecating interfaces breaks the COM contract so it will probably be there for the foreseeable future.&amp;nbsp; The only time I saw esri deprecate interfaces is when they deprecated the class too.&amp;nbsp; if you look at the classes that implement IFeatureLayer2 and compare to the classes that implement IFeatureLayer, you will notice not all classes the implement IFeatureLayer, implement IFeatureLayer2, so for those you have no choice.&amp;nbsp; ArcObjects is littered with 2, 3, 4... interfaces for the precise reason that COM forbids modifying a published interface so if you have a compelling reason to use IFeatureLayer (maybe the method you want to use returns IFeatureLayer or takes it in,) then you are fine.&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks for the response! It also appears IFeatureLayer2 does not contain everything IFeatureLayer has so its doesn't appear to be a replacement even though they say it supercedes it.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Oct 2012 18:12:22 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcobjects-sdk-questions/ifeaturelayer-vs-ifeaturelayer2/m-p/703527#M18845</guid>
      <dc:creator>WayneGuidry</dc:creator>
      <dc:date>2012-10-22T18:12:22Z</dc:date>
    </item>
  </channel>
</rss>

