<?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: NET wrapper - COM interop? in File Geodatabase API Questions</title>
    <link>https://community.esri.com/t5/file-geodatabase-api-questions/net-wrapper-com-interop/m-p/47795#M88</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;Why not just use the C++ version of the API?&lt;BR /&gt;&lt;BR /&gt;I am not sure what advantage there would be in adding a COM interop to the .NET version of the API.&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Because my language of choice is not C++. It is Delphi.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;COM DLLs are language independent, C++ DLLs are not - they can only be used by exes compiled using the same version of Microsoft Visual C++.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have written a quick wrapper DLL in C++, which 'flattens' all the C++ classes in the FGDB API that I am using at present, and exports them as stdcall functions. This is workable, but not ideal.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;A COM wrapper would be much more forward compatible, and provide even more platform neutrality than the .NET wrapper.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;cheers,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Chris&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 02 Sep 2011 14:40:40 GMT</pubDate>
    <dc:creator>ChrisMorgan1</dc:creator>
    <dc:date>2011-09-02T14:40:40Z</dc:date>
    <item>
      <title>NET wrapper - COM interop?</title>
      <link>https://community.esri.com/t5/file-geodatabase-api-questions/net-wrapper-com-interop/m-p/47793#M86</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It is really great to see that V1.1 of the File GDB API is now accessible from .NET applications.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Is there any chance of adding COM interoperability, so that we can use the API from non-NET languagues on Windows?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Chris&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Aug 2011 12:45:58 GMT</pubDate>
      <guid>https://community.esri.com/t5/file-geodatabase-api-questions/net-wrapper-com-interop/m-p/47793#M86</guid>
      <dc:creator>ChrisMorgan1</dc:creator>
      <dc:date>2011-08-24T12:45:58Z</dc:date>
    </item>
    <item>
      <title>Re: NET wrapper - COM interop?</title>
      <link>https://community.esri.com/t5/file-geodatabase-api-questions/net-wrapper-com-interop/m-p/47794#M87</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Why not just use the C++ version of the API?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I am not sure what advantage there would be in adding a COM interop to the .NET version of the API.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Aug 2011 17:05:57 GMT</pubDate>
      <guid>https://community.esri.com/t5/file-geodatabase-api-questions/net-wrapper-com-interop/m-p/47794#M87</guid>
      <dc:creator>DavidSousa</dc:creator>
      <dc:date>2011-08-29T17:05:57Z</dc:date>
    </item>
    <item>
      <title>Re: NET wrapper - COM interop?</title>
      <link>https://community.esri.com/t5/file-geodatabase-api-questions/net-wrapper-com-interop/m-p/47795#M88</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;Why not just use the C++ version of the API?&lt;BR /&gt;&lt;BR /&gt;I am not sure what advantage there would be in adding a COM interop to the .NET version of the API.&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Because my language of choice is not C++. It is Delphi.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;COM DLLs are language independent, C++ DLLs are not - they can only be used by exes compiled using the same version of Microsoft Visual C++.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have written a quick wrapper DLL in C++, which 'flattens' all the C++ classes in the FGDB API that I am using at present, and exports them as stdcall functions. This is workable, but not ideal.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;A COM wrapper would be much more forward compatible, and provide even more platform neutrality than the .NET wrapper.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;cheers,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Chris&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Sep 2011 14:40:40 GMT</pubDate>
      <guid>https://community.esri.com/t5/file-geodatabase-api-questions/net-wrapper-com-interop/m-p/47795#M88</guid>
      <dc:creator>ChrisMorgan1</dc:creator>
      <dc:date>2011-09-02T14:40:40Z</dc:date>
    </item>
    <item>
      <title>Re: NET wrapper - COM interop?</title>
      <link>https://community.esri.com/t5/file-geodatabase-api-questions/net-wrapper-com-interop/m-p/47796#M89</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I'm using Delphi too but for me a better solution would be to have clean C API. A temporary solution is to have own C wrapper or use existing via GDAL. I hope that if .NET developers got the API, a similar C API can be created soon. We waited a long time for this SDK so please satisfy all programmers &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Artur&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Nov 2011 09:39:26 GMT</pubDate>
      <guid>https://community.esri.com/t5/file-geodatabase-api-questions/net-wrapper-com-interop/m-p/47796#M89</guid>
      <dc:creator>ArturRedzko</dc:creator>
      <dc:date>2011-11-15T09:39:26Z</dc:date>
    </item>
    <item>
      <title>Re: NET wrapper - COM interop?</title>
      <link>https://community.esri.com/t5/file-geodatabase-api-questions/net-wrapper-com-interop/m-p/47797#M90</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Keep in mind that the ArcObjects file geodatabase code is written in C++. This is what has been&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ported into the FileGDB API. Esri has no plan to re-write the file geodatabase API in 'C'.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- V&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Nov 2011 11:39:37 GMT</pubDate>
      <guid>https://community.esri.com/t5/file-geodatabase-api-questions/net-wrapper-com-interop/m-p/47797#M90</guid>
      <dc:creator>VinceAngelo</dc:creator>
      <dc:date>2011-11-15T11:39:37Z</dc:date>
    </item>
    <item>
      <title>Re: NET wrapper - COM interop?</title>
      <link>https://community.esri.com/t5/file-geodatabase-api-questions/net-wrapper-com-interop/m-p/47798#M91</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I don't want you to re-write the file geodatabase API in 'C', just add additional C API wrapper like for .NET. A good example here is GDAL library where most code is in C++ but there is additional C API wrapper around. It can be simplified to limit work required.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Nov 2011 09:44:25 GMT</pubDate>
      <guid>https://community.esri.com/t5/file-geodatabase-api-questions/net-wrapper-com-interop/m-p/47798#M91</guid>
      <dc:creator>ArturRedzko</dc:creator>
      <dc:date>2011-11-18T09:44:25Z</dc:date>
    </item>
  </channel>
</rss>

