ArcGIS Engine Developer Guide

More documents

Recommendations

Info

ARCGIS SOFTWARE ARCHITECTURE Although the changes required for software created for use with ArcGIS 8 to work with ArcGIS 9 are minimal, it is important to understand that to realize any existing investment in the ArcObjects architecture at ArcGIS 9, you must review your developments with respect to ArcGIS Engine, ArcGIS Server, and ArcGIS Desktop. ESRI understands the importance of a unified software architecture and has made numerous changes for ArcGIS 9 so the investment in ArcObjects can be realized on multiple products. If you have been involved in creating extensions to the ArcGIS architecture for ArcGIS 8, you should think about how the new ArcGIS 9 architecture affects the way your components are implemented. 28 • ArcGIS Engine Developer Guide
ARCGIS APPLICATION PROGRAMMING INTERFACES It is important not to confuse the Visual C++ support available through the COM API and the native C++ API. Since ArcObjects is developed in C++, there are some cases in which data types compatible with C++ have been used for performance reasons. These performance considerations mostly affect the internals of ArcObjects; therefore, using one of the generic interfaces should not adversely affect performance of your ArcObjects developments. The functionality of ArcObjects can be accessed using four application programming interfaces. The choice of which API to use is not a simple one and will depend on a number of factors including the ArcGIS product that you are developing with, the end user functionality that you are developing, and your development experience with particular languages. ArcGIS Engine supports the following APIs: • COM—Any COM-compliant language (for example, Visual Basic and Visual C++) can be used with this API. • .NET—Visual Basic .NET and C# are supported by this API. • Java—Sun Java 2 Platform, Standard Edition (J2SE). • C++—Microsoft Visual C++ 6.0, Microsoft Visual C++ .NET 2003, Sun Solaris Forte 6 Update 2, Linux GCC 3.2. When working with ArcObjects, developers can consume functionality exposed by ArcObjects or extend the functionality of ArcObjects with their own components. When referring to these APIs, there are differences with respect to consuming and extending the ArcObjects architecture. CONSUMING API All four APIs support consuming the functionality of ArcObjects; however, not all interfaces implemented by ArcObjects are supported on all platforms. In some cases interfaces make use of data types that are not compatible with an API. In situations like this, an alternative implementation of the interface is provided for developers to use. The naming convention of a “GEN” suffix on the interface name is used to signify this kind of interface; IFoo would have an IFooGEN interface. This alternative interface is usable by all APIs; however, if the nongeneric interface is supported by the API, it is possible to continue to use the API-specific interface. EXTENDING API Extending ArcObjects entails creating your own objects and adding them to the ArcObjects architecture. ArcObjects is written to be extensible in almost all areas. Support for extending the architecture varies among the APIs and, in some cases, varies among languages of an API. The COM API provides the most possibilities for extending the system. The limitation within this API is with Visual Basic language. Visual Basic does not support the implementation of interfaces that have one or more of the following characteristics: • The interface inherits from an interface other than IUnknown or IDispatch. For example, ICurve, which inherits from IGeometry, cannot be implemented in VB for this reason. • Method names on an interface start with an underscore (“_”). You will not find functions beginning with “_” in ArcObjects. • A parameter of a method uses a data type not supported by Visual Basic. IActiveView cannot be implemented in Visual Basic for this reason. Chapter 2 • ArcGIS software architecture • 29
Page 1 and 2: ArcGIS ® Engine Developer Guide Ar
Page 3 and 4: Contents CHAPTER 1: INTRODUCING ARC
Page 5 and 6: 1 Introducing ArcGIS Engine ESRI ®
Page 7 and 8: ARCGIS 9 OVERVIEW ArcGIS Server Arc
Page 9 and 10: ARCGIS 9 OVERVIEW ArcGIS Engine and
Page 11 and 12: OVERVIEW OF ARCGIS ENGINE Chapter 3
Page 13 and 14: OVERVIEW OF A RCGIS ENGINE The Stre
Page 15 and 16: WHO CAN USE ARCGIS ENGINE? authored
Page 17 and 18: ARCGIS ENGINE CAPABILITIES SPATIAL
Page 19 and 20: ARCGIS ENGINE CAPABILITIES NETWORK
Page 21 and 22: GETTING STARTED Throughout most of
Page 23 and 24: USING THIS BOOK This book, ArcGIS E
Page 25: DEVELOPER RESOURCES ESRI DEVELOPER
Page 28 and 29: ARCGIS SOFTWARE ARCHITECTURE For a
Page 30 and 31: ARCGIS SOFTWARE ARCHITECTURE ESRI h
Page 34 and 35: ARCGIS APPLICATION PROGRAMMING INTE
Page 36 and 37: ARCGIS ENGINE LIBRARIES Carto Conta
Page 38 and 39: ARCGIS ENGINE LIBRARIES cluded in t
Page 40 and 41: ARCGIS ENGINE LIBRARIES 22 Spatial-
Page 42 and 43: ARCGIS ENGINE LIBRARIES NETWORKANAL
Page 45 and 46: 3 Developing with ArcGIS controls A
Page 47 and 48: WORKING WITH THE ARCGIS CONTROLS me
Page 49 and 50: WORKING WITH THE ARCGIS CONTROLS Ar
Page 51 and 52: WORKING WITH THE ARCGIS CONTROLS If
Page 53 and 54: WORKING WITH THE ARCGIS CONTROLS Li
Page 55 and 56: BUILDING APPLICATIONS WITH THE ARCG
Page 57 and 58: BUILDING APPLICATIONS WITH THE ARCG
Page 59: BUILDING APPLICATIONS WITH THE ARCG
Page 62 and 63: THE MICROSOFT COMPONENT OBJECT MODE
Page 74 and 75: DEVELOPING WITH ARCOBJECTS ArcGIS a
Page 76 and 77: DEVELOPING WITH A RCOBJECTS Accessi
Page 78 and 79: DEVELOPING WITH A RCOBJECTS As an e
Page 80 and 81: DEVELOPING WITH A RCOBJECTS COM App
Page 82 and 83:
DEVELOPING WITH A RCOBJECTS The Cus
Page 84 and 85:
THE V ISUAL BASIC 6 ENVIRONMENT Use
Page 86 and 87:
THE V ISUAL BASIC 6 ENVIRONMENT Whi
Page 88 and 89:
THE V ISUAL BASIC 6 ENVIRONMENT Pri
Page 90 and 91:
THE V ISUAL BASIC 6 ENVIRONMENT Tha
Page 92 and 93:
THE V ISUAL BASIC 6 ENVIRONMENT per
Page 94 and 95:
THE V ISUAL BASIC 6 ENVIRONMENT If
Page 96 and 97:
THE V ISUAL BASIC 6 DEVELOPMENT ENV
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
VISUAL C++ IXxxImpl CComXxxThreadMo
Page 106 and 107:
VISUAL C++ Linking ATL code One of
Page 108 and 109:
VISUAL C++ removal would result in
Page 110 and 111:
VISUAL C++ switches are used to cha
Page 112 and 113:
VISUAL C++ 4. To create the noncrea
Page 114 and 115:
VISUAL C++ Grimes, Richard, Reilly
Page 116 and 117:
VISUAL C++ IFooPtr ipFoo; HRESULT h
Page 118 and 119:
VISUAL C++ expected. It is better t
Page 120 and 121:
VISUAL C++ Here are some suggestion
Page 122 and 123:
VISUAL C++ Symbol d, i Format signe
Page 124 and 125:
VISUAL C++ Loading the following sh
Page 126 and 127:
VISUAL C++ #import "C:\Program File
Page 128 and 129:
VISUAL C++ Make sure dialog boxes t
Page 130 and 131:
VISUAL C++ Creating an MFC dialog b
Page 132 and 133:
VISUAL C++ This environment does no
Page 134 and 135:
VISUAL C++ Connection point mechani
Page 136 and 137:
VISUAL C++ The following issues wit
Page 138 and 139:
VISUAL C++ { } DECLARE_REGISTRY_RES
Page 140 and 141:
VISUAL C++ 5. Clicking OK will modi
Page 142 and 143:
VISUAL C++ delete[] pvars; // Clean
Page 144 and 145:
VISUAL C++ // Create dialog class o
Page 146 and 147:
.NET APPLICATION PROGRAMMING INTERF
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
JAVA APPLICATION PROGRAMMING INTERF
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
C++ APPLICATION PROGRAMMING INTERFA
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
Page 257 and 258:
5 Licensing and deployment Developm
Page 259 and 260:
ARCGIS LICENSING OPTIONS PRODUCT LI
Page 261 and 262:
ARCGIS LICENSING OPTIONS ArcGIS Eng
Page 263 and 264:
ARCGIS ENGINE DEVELOPER KIT At the
Page 265 and 266:
APPLICATION DEVELOPMENT AND LICENSE
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
TESTING WITH ARCGIS ENGINE RUNTIME
Page 281 and 282:
DEPLOYMENT To successfully deploy c
Page 283 and 284:
DEPLOYMENT 3. You or your client in
Page 285 and 286:
6 Developer scenarios Throughout th
Page 287 and 288:
BUILDING APPLICATIONS WITH ACTIVEX
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
BUILDING APPLICATIONS WITH VISUAL J
Page 311 and 312:
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
Page 319 and 320:
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Page 327 and 328:
Page 329 and 330:
Page 331 and 332:
Page 333 and 334:
Page 335 and 336:
BUILDING APPLICATIONS WITH WINDOWS
Page 337 and 338:
Page 339 and 340:
Page 341 and 342:
Page 343 and 344:
Page 345 and 346:
Page 347 and 348:
Page 349 and 350:
Page 351 and 352:
Page 353 and 354:
Page 355 and 356:
Page 357 and 358:
Page 359 and 360:
Page 361 and 362:
BUILDING APPLICATIONS WITH C++ AND
Page 363 and 364:
Page 365 and 366:
Page 367 and 368:
Page 369 and 370:
Page 371 and 372:
Page 373 and 374:
Page 375 and 376:
Page 377 and 378:
Page 379 and 380:
Page 381 and 382:
Page 383 and 384:
Page 385 and 386:
Page 387 and 388:
Page 389 and 390:
Page 391 and 392:
Page 393 and 394:
Page 395 and 396:
Page 397 and 398:
Page 399 and 400:
Page 401 and 402:
Page 403 and 404:
Page 405 and 406:
Page 407 and 408:
Page 409 and 410:
Page 411 and 412:
Page 413 and 414:
BUILDING A COMMAND-LINE JAVA APPLIC
Page 415 and 416:
Page 417 and 418:
Page 419 and 420:
Page 421 and 422:
Page 423 and 424:
Page 425 and 426:
Page 427 and 428:
Page 429 and 430:
Page 431 and 432:
BUILDING A COMMAND-LINE C++ APPLICA
Page 433 and 434:
Page 435 and 436:
Page 437 and 438:
Page 439 and 440:
Page 441 and 442:
Page 443 and 444:
Page 445 and 446:
A Reading the object model diagrams
Page 447 and 448:
CLASSES AND RELATIONSHIPS There are
Page 449 and 450:
CLASSES AND RELATIONSHIPS N-ary ass
Page 451 and 452:
INTERFACES AND MEMBERS error messag
Page 453:
PUTTING IT TOGETHER—AN EXAMPLE IW
Page 456 and 457:
ARCGIS SOFTWARE DEVELOPER KIT The A
Page 458 and 459:
ARCGIS SOFTWARE DEVELOPER KIT • E
Page 461 and 462:
C Conver erting personal geodatabas
Page 463 and 464:
CONVERTING DATA FOR USE WITH THE GI
Page 465 and 466:
CONVERTING DATA FOR USE WITH THE GI
Page 467 and 468:
D Installing ArcGIS Engine Runtime
Page 469 and 470:
INSTALLING ARCGIS ENGINE RUNTIME ON
Page 471 and 472:
Page 473 and 474:
Page 475 and 476:
Page 477 and 478:
Page 479 and 480:
Page 481 and 482:
Page 483 and 484:
Page 485 and 486:
Page 487 and 488:
Page 489 and 490:
Page 491 and 492:
Page 493 and 494:
Page 495 and 496:
E Glossary The following is a gloss
Page 497 and 498:
GLOSSARY ASP.NET assembly associati
Page 499 and 500:
GLOSSARY composition computer-aided
Page 501 and 502:
GLOSSARY FGDC framework GDB GDI Geo
Page 503 and 504:
GLOSSARY JSF JSP JSTL late binding
Page 505 and 506:
GLOSSARY the EXE in which they are
Page 507 and 508:
GLOSSARY server account server cont
Page 509 and 510:
GLOSSARY URL usage time utility COM
Page 511 and 512:
A Index Abstract class 61 defined 4
Page 513 and 514:
Building applications with ActiveX
Page 515 and 516:
debugging defined 495 Deeply statef
Page 517 and 518:
IIS 143 ILineSymbol interface 292,
Page 519 and 520:
OLE automation. See Microsoft Compo
Page 521 and 522:
SXD defined 504 Synchronization def
Page 523:
XSLT defined 506 Index • 519
show all

ArcGIS Engine Developer Guide

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?