ArcGIS Engine Developer Guide

More documents

Recommendations

Info

ARCGIS LICENSING OPTIONS For more detailed descriptions of the features provided by the ArcGIS Engine extensions, see Chapter 1, ‘Introducing ArcGIS Engine’. All editing of datasets is subject to the standard editing restrictions in the core ESRI products. Methods for leveraging multiple levels of licensing in this manner are discussed in the section, ‘License initialization’. The extended ArcGIS Engine features and the extension runtime licenses that can be used to initialize them are: • Multiuser enterprise geodatabase—ArcGIS Engine Runtime with Geodatabase Update extension or an ArcEditor or ArcInfo license. • Visualization of data in 3D, GlobeControl, and SceneControl—ArcGIS Engine Runtime with 3D extension or an ArcGIS Desktop (ArcView, ArcEditor, or ArcInfo) license with the 3D Analyst extension. • Creation and analysis of cell-based raster data—ArcGIS Engine Runtime with Spatial extension or an ArcGIS Desktop (ArcView, ArcEditor, or ArcInfo) license with the ArcGIS Spatial Analyst extension. • Creation and management of network datasets and network-based spatial analysis—ArcGIS Engine Runtime with the Network extension or an ArcGIS Desktop (ArcView, ArcEditor, or ArcInfo) license with the ArcGIS Network Analyst extension. ArcGIS Engine Runtime with Network extension can: • Create, update, and delete networks on shapefiles, SDC, and pGDB. • Solve any network. ArcGIS Engine Runtime with the Geodatabase Update and the Network extension can: • Create, update, and delete networks on shapefiles, SDC, pGDB, and GDB. • Solve any network. ARCGIS ENGINE AND ARCGIS DESKTOP LICENSING One advantage of ArcGIS Engine mentioned in previous chapters is the fact that it is the platform used for the ArcGIS Desktop applications. This allows for more flexibility in the licensing of your application. In some cases, you may wish to deploy an ArcGIS Engine-based application that can utilize either the core ArcGIS Engine Runtime product and extension licenses or the equivalent ArcGIS Desktop product and extension licenses. The following table lists the ArcGIS Engine product or extension license and its equivalent ArcGIS Desktop license. 256 • ArcGIS Engine Developer Guide
ARCGIS LICENSING OPTIONS ArcGIS Engine ArcGIS Engine Runtime ArcGIS Engine with Geodatabase Update extension ArcGIS Engine with 3D extension ArcGIS Engine with Spatial extension ArcGIS Engine Runtime with the Network extension ArcGIS Desktop ArcView ArcEditor ArcGIS Desktop (ArcView, ArcEditor, or ArcInfo) with 3D Analyst ArcGIS Desktop (ArcView, ArcEditor, or ArcInfo) with Spatial Analyst ArcGIS Desktop (ArcView, ArcEditor, or ArcInfo) with Network Analyst License comparison ArcGIS Engine Runtime is functionally equivalent to ArcView at the ArcObjects level. ArcGIS Engine Runtime does not include any of the ArcGIS Desktop applications, such as ArcMap, but it does include the same core GIS ArcObjects. ArcGIS Engine Runtime with the Geodatabase Update extension is functionally equivalent to ArcEditor at the ArcObjects level. The Geodatabase Update extension does not include any of the advanced editing tools available in ArcMap, but it does provide complete access to the Geodatabase API for creating, editing, and managing an enterprise geodatabase. ArcGIS Engine Runtime with the 3D extension is functionally equivalent to ArcGIS Desktop with the 3D Analyst extension at the ArcObjects level. The 3D extension for ArcGIS Engine does not include the ArcScene or ArcGlobe applications, but it does provide access to the GlobeControl and SceneControl for embedding 3D visualization in custom applications. ArcGIS Engine Runtime with the Spatial extension is functionally equivalent to ArcGIS Desktop with the Spatial Analyst extension at the ArcObjects level. The Spatial extension for ArcGIS Engine does not include the ArcGIS Desktop toolbars or commands, but it does provide the ArcObjects components necessary for raster cell analysis. ArcGIS Engine Runtime with the Network extension is functionally equivalent to ArcGIS Desktop with the Network Analyst extension at the ArcObjects level. The ArcGIS Engine Network extension does not include the ArcGIS Desktop toolbars or commands, but it does provide the ArcObjects components necessary for creating custom applications that solve on any network. Chapter 5 • Licensing and deployment • 257
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 32 and 33:
ARCGIS SOFTWARE ARCHITECTURE Althou
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:
Page 59:
Page 62 and 63:
THE MICROSOFT COMPONENT OBJECT MODE
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
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: C++ APPLICATION PROGRAMMING INTERFA
Page 257 and 258: 5 Licensing and deployment Developm
Page 259: ARCGIS LICENSING OPTIONS PRODUCT LI
Page 263 and 264: ARCGIS ENGINE DEVELOPER KIT At the
Page 265 and 266: APPLICATION DEVELOPMENT AND LICENSE
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 309 and 310: BUILDING APPLICATIONS WITH VISUAL J
Page 311 and 312:
BUILDING APPLICATIONS WITH VISUAL J
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?