Bug
A custom geoprocessing function tool created with Visual C++ fails to run in ArcGIS 10 when background geoprocessing is enabled, or displays a pure virtual function error upon closing the application.
| Bug ID Number | NIM066767 |
|---|---|
| Submitted | March 31, 2011 |
| Last Modified | June 5, 2024 |
| Applies to | ArcGIS for Desktop |
| Version found | 10.0 |
| Program language | VC++ |
| Operating System | Windows OS |
| Operating System Version | Vista |
| Status | Known Limit |
Additional Information
This is as designed only because we have no control over how someone creates a custom GP tool. There are certain constraints assoicated with running in the Background which must be followed. .Net based tools for the most part donot run well in the Background. Custom GP Tool developers whose tools don''t work in the backgound need to implement the following interface: // // IGPToolBackground interface... // [ oleautomation, local, object, uuid(632F8246-0681-4222-9080-48AD9FADADE7), pointer_default(unique), helpcontext(95195), helpstring("Tool Background Implementation Interface."), ] interface IGPToolBackground : IUnknown { [ propget, helpcontext(95196), helpstring("Can this tool run in the background."), ] HRESULT CanRunInBackground([out, retval] VARIANT_BOOL* pCanRunInBackground); [ propput, helpcontext(95197), helpstring("Can this tool run in the background."), ] HRESULT CanRunInBackground([in] VARIANT_BOOL canRunInBackground); }; And have it return VARIANT_FALSE for get_CanRunInBackground.Steps to Reproduce
Bug ID: NIM066767
Software:
- ArcGIS for Desktop
Get notified when the status of a bug changes
Discover more on this topic
Search for related information
Find training related to this topic
Explore ideas and give feedback
Get help from ArcGIS experts
Download the Esri Support App