1

I have an application that does many operations including some Geoprocessor tasks.

Should I create a single Geoprocessor() object for the lifetime of the application or should I create a new one each time I want to use a Geoprocessor tool?

Improve this question

1 Answer 1

Reset to default
2

I develop and maintain a tool built in VB .net which makes use of the IGeoProcessor. When my code calls a function that uses it, it creates and destroys within the function. I've seen no particular drop in performance. There may be a small cost in instantiating it but that seems to be trivial when compared to what tools it executes.

As long as its not being created and destroyed say in an inner loop within a function then I think you are OK in creating it and destroying it within a function, well that's what I do.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.