COM will follow the same path that VB6 and VBA have. Have you noticed that the C++ SDK for 10 has been relegated to a few notes in help? Not much love there either. For Microsoft platforms, ESRI is moving towards pure .NET. Look at add-ins in 10. Look how they removed component catagories from the registry. Everything that ESRI (and Microsoft) is doing and showing is .NET. How many books in print can you still buy on COM? The death of COM cometh. At the recent developers summit, ESRI provided additional hints of this in their work on 10.1 and beyond.
I hope the COM support continues because most of my work is in C++ using COM.Can you elaborate on "death of COM cometh"?Thank you!
COM remains and is supported.VB6 code does work because it is based on COM.ESRI dropped support for VB6.
COM is a very fundamental element of the ESRI stack. This is how they maintain a single C++ code based for ArcObjects which is able to execute on both the Microsoft and Java technology stacks. That said, it seems clear to me that the death of COM cometh.
(1) Does this also mean that COM API is also gone from ArcObjects? If not, then VB should continue to work, right?
Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.