Comparison with COM API

[GoogleCodeExporter]

[not really an issue as such]

How would you compare this with the Google Earth COM API?
http://earth.google.com/comapi/index.html 

Given VS kicks out a PIA for this, isn't that all the managed code wrapper 
we need?

Original issue reported on code.google.com by piers.wi...@gmail.com on 8 Dec 2009 at 3:48

[GoogleCodeExporter]

No worries, the main difference is that the COM Api is unsupported by Google 
and is no 
longer in development, whilst the javascript Api is. 

http://groups.google.com/group/kml-support-com-
api/browse_thread/thread/fd6c4fe966a1eaf7

Original comment by fraser.c...@gmail.com on 8 Dec 2009 at 9:47

• Added labels: Type-Other
• Removed labels: Type-Defect

[GoogleCodeExporter]

Original comment by fraser.c...@gmail.com on 7 Mar 2010 at 5:17

• Changed state: Done
• Added labels: OpSys-Windows

[GoogleCodeExporter]

Also, just to note the - early binding on the earth client is a nightmare for 
any kind of distributed application as the Interop assemblies need rebuilding 
at each Google Earth version update. If I wasn't using the DLR I would still 
not use the PIA, I would go the reflection route...

Original comment by fraser.c...@gmail.com on 7 Feb 2012 at 8:20