registered trademarks of their respective trademark owners. Environmental Systems Research Institute, Inc. Exploring ArcObjects. Volume 1—Applications and. Note: simply for learning the ArcObjects API & regardless of doing C# nor VBA can: a REPL — one of the best ways to explore an API by far. Exploring ArcObjects provides the foundation for carrying out your development taskswhether writing simple VBA scripts for customizing ArcGIS applications.

Author: Zulkimi Faujinn
Country: Burundi
Language: English (Spanish)
Genre: Career
Published (Last): 2 July 2018
Pages: 158
PDF File Size: 12.17 Mb
ePub File Size: 4.18 Mb
ISBN: 208-2-42505-139-1
Downloads: 25139
Price: Free* [*Free Regsitration Required]
Uploader: Fausho

By using our site, you acknowledge that you have read and understand our Cookie PolicyPrivacy Policyand our Terms of Service.

While I understand that this may be off topic to an extent, I am in a bit of a bind and could use some help directing my thought process and research.

I have little programming background aside from: This has worked just fine for me so far, but there appears to be a need for me to move into a. A decision is being made by my management with some direction from me on whether the company should move forward and create a standard for coding in ArcObjects that is aimed at using VB or C.

The main considerations since I am the only person who will be taking part in this are future extendability, “safety” of code, and readability. Most of these concerns appear to be things that can be dealt with in the writing of the code as opposed to the language itself, but I don’t know enough to be certain. I’ve read an article or two comparing C to VB in terms of. NET, but I would like to ask for further reasoning to consider when deciding on one language over another for a person of my background.

What are the most important things to keep in mind when choosing which of the two languages to begin study in for use with ArcObjects? Responses have been great. I went with Dan’s answer since it covered all the ground I asked about and went the extra step to point me at IPython.

Mine would be strongly in the C camp, as VB.

However, given your specific situation, I would actually float a different idea, specifically IronPython. You will be living on an obscure and bleeding edgeespecially within the ESRI community but even to some extent in the larger. You’ll spend some time troubleshooting obscure bugs that come from the impedance mismatch of several layers of abstraction: You get to explore an obscure and bleeding edge, lighting the way for the ESRI and.


NET communities to follow in your footsteps! You can keep working in python until you hit other limitations and make the move to other. NET languages a gradual one instead of a sharp transition: Your existing python geoprocessing scripts will be somewhat portable the GP object is visible in.

Exploring ArcObjects

NET-land too, and IronPython supports IDispatch so there’s a chance they might be directly portable with just a few code-line changes. For someone entering the. NET world, it’s better to take advantage of the fact you are essentially in a learning process and incorporate taking on C in it as well. I will not compare the two languages here as there has been plenty written about them, as well as many pointless flamewars fought.

Here’s my two cents coming from extensive experience with both of them along with few other languages:. C is much more readable and natural in the. It is THE prominent language to develop in on. Microsoft is heavily investing in it, it evolves quickly and has recently incorporated some features of functional languages which will get under your skin easily.

NET is and will be sort of kept around, but new features and tooling are almost always first available in C.

Exploring ArcObjects – Esri

In another words, both are first-class. NET citizens, but they are not exactly equal. NET, which does not hold true explring C 4. Note you can take advantage of some C 4 features and still compile your code to target. So in my opinion, only if you have large legacy codebase in VB which you cannot afford to rewrite, go with VB. Otherwise there is no dxploring why not to get your job done in the cutting-edge. NET language which is C. There are arcobjectx few differencesbut they both offer similar features like exception handling, etc.

Furthermore, documentation from Esri and Microsoft typically provide examples for equivalent operations in both VB. It really comes down to the preferences of your development team or yourself, if you are the team.

This is not intended as an answer per se, but is submitted in reference to the IronPython answer posted by Exploging S. I was struggling to trace ArcObjects calls in Oracle, and thought that it would be easier with Python because I could issue calls interactively and see immediately what the trace output looked like.

I never got that far, but I did write this little testing script. By clicking “Post Your Answer”, you acknowledge that you have read our updated terms of serviceprivacy policy and cookie policyand that your continued use of the website is subject to these policies. Home Questions Tags Users Unanswered.


Sorry if this is too verbose! I simply want my need to be understood. Nathanus 3, 1 25 C is easier to read because its less verbose, there are more C jobs overall, and I will be really surprised if you can do something with VB. NET that you can’t do with C. NET vs C really does come down to, mostly, a matter of opinion. It seems a fantastic match for this need: I really wish more people were doing this.

And if they are; I wish they were publicising it! The COM interop is not as convenient as it could be, though. Moreover, while I love IronPython, I would not recommend it to someone who is just starting with ArcObjects since the additional layer of interop and abstraction can be easily confusing for beginners.

If you’ve been doing this, it would be awesome if you wrote it up!

Mar 29 arcobjectw at IronPython works well with ArcObjects, in my limited experience. The biggest frustration is the lack of native Python support for interfaces, and ArcObjects is almost entirely based on interfaces.

Support for properties is also missing. This means that many calls will look goofy compared to the documentation. Here’s my two cents coming from extensive experience with both of them along with few other languages: Petr Krebs 9, 1 17 So here it is: GetValue gds set up tracing IWorkspace.

Exploring ArcObjects : Michael Zeiler :

NextRow c while r is not None: Thanks for this — Something arcojects the expliring the interfaces are working doesn’t ring right — but I’ve yet to use IronPython with ArcObjects. It may also be an issue with how long ago you did this IronPython is a fairly active project. I don’t have a local DB right now, so I can’t try it exactly, but maybe I’ll do a test sooner rather than later. Mar 30 ’11 at Dan — It’s pretty fresh: Sign up or log in Sign up using Google.

Sign up using Facebook. Sign up using Email and Password. Post as a guest Agcobjects. Email Required, but never shown. Post Your Answer Discard By clicking “Post Your Answer”, you acknowledge that you have read our updated terms of serviceprivacy policy and cookie policyand that your continued use of the website is subject to these policies.