1. Esri UC2013. Technical Workshop. Technical Workshop 2013 Esri International User Conference July 8–12, 2013 | San Diego, California Developing.NET Applications for ArcGIS Engine Deep Dhanasekaran and John Hauck

2. Esri UC2013. Technical Workshop. Agenda Introduction to Engine Controls SDK Requirements Runtime Binding Authoring content for ArcGIS Engine Adding functionality to ArcGIS Engine ArcGIS Engine and ArcGIS Runtime Developing.NET Applications for ArcGIS Engine

3. Esri UC2013. Technical Workshop. Introduction to.NET Creating.NET Add-Ins for ArcGIS for Desktop

4. Esri UC2013. Technical Workshop. Development framework to build applications for the Windows Platform Key Features - Common Language Runtime - Interoperability - Base Class Library - Windows Forms What is.NET? Creating.NET Add-Ins for ArcGIS for Desktop

5. Esri UC2013. Technical Workshop. Coded solutions to common programming problems - Interacting with databases - Parsing XML - File reading and writing - String manipulation - Working with collections Base Class Library Creating.NET Add-Ins for ArcGIS for Desktop

6. Esri UC2013. Technical Workshop. Tools and Controls to build GUIs - Toolbars and Menus - Text Box, Combo Box, List View, Button - Layout and Data Binding Events driven Windows Forms Creating.NET Add-Ins for ArcGIS for Desktop

7. Esri UC2013. Technical Workshop. When building your add-in you need to target a specific version of.NET 3.5 is recommended for 10, 10.1 and 10.2 -.NET 3.5 is required for ArcGIS Desktop 4.0 is supported at 10.1 and 10.2 Supported.NET Versions Creating.NET Add-Ins for ArcGIS for Desktop

8. Esri UC2013. Technical Workshop. VB.NET - Syntax closest to VBA and VB6 C# - Syntax similar to C++ & Java No difference in performance Same access to.NET BCL and ArcObjects API Selecting a Language Creating.NET Add-Ins for ArcGIS for Desktop

9. Esri UC2013. Technical Workshop. Where to write your code? Integrated Development Environment (IDE) - Source code editor, Debugger Visual Studio - Visual Studio 2008 (10.0) - Visual Studio 2010 (10*, 10.1, 10.2) - Visual Studio 2012 (10.2) - Free express version is supported - *2010 VS Express not supported at 10.0 Creating.NET Add-Ins for ArcGIS for Desktop

10. Esri UC2013. Technical Workshop. One IDE for all.NET projects - Templates Code Editor - Syntax highlighting, code completion Debugger Windows Forms Designer - Drag/Drop controls Visual Studio Key Features Creating.NET Add-Ins for ArcGIS for Desktop

11. Esri UC2013. Technical Workshop. What is ArcGIS Engine? Developing.NET Applications for ArcGIS Engine

12. Esri UC2013. Technical Workshop. What is ArcGIS Engine? Product used to build custom standalone GIS solutions - ArcObjects - ArcGIS Engine Controls Leverage the power of ArcGIS Desktop and Server - Use Desktop to author content - Use Engine to consume content Developing.NET Applications for ArcGIS Engine

13. Esri UC2013. Technical Workshop. Where to write your code? Integrated Development Environment (IDE) - Source code editor, Debugger Visual Studio - Visual Studio 2008 (10.0) - Visual Studio 2010 (10*, 10.1, 10.2) - Visual Studio 2012 (10.2) - Free express version is supported - *2010 VS Express not supported at 10.0 Creating.NET Add-Ins for ArcGIS for Desktop

14. Esri UC2013. Technical Workshop. When building your application you need to target a specific version of.NET 3.5 is recommended for 10, 10.1 and 10.2 -.NET 3.5 is required for ArcGIS Desktop 4.0 is supported at 10.1 and 10.2 - Need to handle distribution - Don’t embed interop types Supported.NET Versions Creating.NET Add-Ins for ArcGIS for Desktop

15. Esri UC2013. Technical Workshop. 64 Bit Support ArcGIS Engine is a 32 bit application - Run as a 32 bit application on 64 bit OS - Target x86 Default is “Any CPU” At Version 10 Engine applications are Large Address Aware When compiling VS 2010 applications on a x64 machine - Follow KB 37879 Developing.NET Applications for ArcGIS Engine

16. Esri UC2013. Technical Workshop. Runtime Binding and Licensing Developing.NET Applications for ArcGIS Engine

17. Esri UC2013. Technical Workshop. Runtime Binding Starting at ArcGIS 10 each product has it’s own runtime - Separate install locations - Service pack products separately - Uninstall service packs ArcObjects must be pointed to a runtime to work - Before any other ArcObjects calls - Required for all standalone applications - Engine applications can bind to either Desktop or Engine Runtimes What is Runtime Binding? Developing.NET Applications for ArcGIS Engine

18. Esri UC2013. Technical Workshop. Runtime Binding Add reference to: ESRI.ArcGIS.Version Bind using the RuntimeManager static class How to bind to a runtime ESRI.ArcGIS.RuntimeManager.Bind(ESRI.ArcGIS.ProductCode.Engine) Developing.NET Applications for ArcGIS Engine

19. Esri UC2013. Technical Workshop. Runtime Binding When and Where - Preferably in your main method (C#) - Preferably in your application events StartUp method (VB) Tip: - The Assembly is called ESRI.ArcGIS.Version - The Namespace is ESRI.ArcGIS - Bind method returns a Boolean that you can use to handle binding errors When to bind to a runtime? Developing.NET Applications for ArcGIS Engine

20. Esri UC2013. Technical Workshop. Runtime Binding RuntimeManager.BindLicense - Bind and License with one method RuntimeCollection - Identify Installed Runtimes RuntimeInfo - Identify the Path, Product, & Version ActiveRuntime - Currently bound runtime Additional Functionality and uses Developing.NET Applications for ArcGIS Engine

21. Esri UC2013. Technical Workshop. Licensing Licenses are checked out at Runtime - Either Desktop or Engine - Licenses are checked out for the life of the application - Extensions can be checked out and returned as needed Concurrent Engine licenses are available starting at 10.0 Licensing is not the same as binding - Binding specifies the runtime - Licensing specifies product functionality Developing.NET Applications for ArcGIS Engine

22. Esri UC2013. Technical Workshop. Licensing Engine ArcView / Basic Geodatabase Update Single UseConcurrent Use Developing.NET Applications for ArcGIS Engine ArcEditor / Standard ArcInfo / Advanced

23. Esri UC2013. Technical Workshop. Controls and Binding Demo demo Developing.NET Applications for ArcGIS Engine

24. Esri UC2013. Technical Workshop. Binding and Deployment ArcGIS Engine is not required on the target machine - Can leverage Desktop or Engine Runtime Can mix and match Licensing and runtime for flexible Engine applications - Leverage existing Desktop licenses and runtime on clients machine Developing.NET Applications for ArcGIS Engine

25. Esri UC2013. Technical Workshop. Content for ArcGIS Engine Developing.NET Applications for ArcGIS Engine

26. Esri UC2013. Technical Workshop. Basemap and RasterBasemap Layers Layers that draw with a high-performance multi- threaded drawing engine - Improves display speed and responsiveness - Seamless display Limitations - Layers in a Basemap Layer have less functionality - Cannot modify layer properties - Some data sources, layer types, and symbols are not supported What are Basemap Layers Developing.NET Applications for ArcGIS Engine

27. Esri UC2013. Technical Workshop. Basemap and RasterBasemap Layers Best to author through ArcMap - Make use of the analyzers for optimization For optimal performance - Test to see if you can enable hardware acceleration - IGlobalScreenDisplaySettings.CanEnableHardwareAcceleration - Enable hardware acceleration - IGlobalScreenDisplaySettings.EnableHardwareAcceleration Using Basemap Layers in Engine Developing.NET Applications for ArcGIS Engine

28. Esri UC2013. Technical Workshop. Working with Packages Packages are a single file - Contains a map or layer[s] and supporting data - Also can contain references to SDE data Easy to share ArcGIS 10.0 supports - Layer Packages (*.lpk) - Map Packages (*.mpk) ArcGIS 10.1 adds additional support for - Geoprocessing Packages (*.gpk) - Locator Packages (*.apk) - Tile Packages (*.tpk) What are packages? Developing.NET Applications for ArcGIS Engine

29. Esri UC2013. Technical Workshop. Working with Packages At ArcGIS 10 sp1 - Programmatically consume packages IMapDocument.Open - Map Packages - Layer Packages - Web Maps ILayerFile.Open - Layer Packages Just point to the path of the package Using Packages in Engine Developing.NET Applications for ArcGIS Engine

30. Esri UC2013. Technical Workshop. Working with Packages Using Packages in Engine Opening Layer Packages Opening Map Packages Developing.NET Applications for ArcGIS Engine

31. Esri UC2013. Technical Workshop. Working with Packages Consume data on ArcGIS Online - Pass in a URL with the id as the filename http://www.arcgis.com/home/item.html?id=a50c645f83bb4f5dbdddd457df29d639 Using Online Content Developing.NET Applications for ArcGIS Engine

32. Esri UC2013. Technical Workshop. Working with Packages Add reference to: ESRI.ArcGIS.EngineCore Unpack using IPackageFile.Unpack Using IPackageFile at 10.1 Developing.NET Applications for ArcGIS Engine

33. Esri UC2013. Technical Workshop. Working with Packages Easily deploy maps, data, and functionality - Simple deployment of a single file - Easy to update off cycle Packages can be uploaded to ArcGIS Online - Once a package is downloaded it can be used locally - Use ArcGIS Online groups to manages access Why use Packages in Engine? Developing.NET Applications for ArcGIS Engine

34. Esri UC2013. Technical Workshop. Adding Functionality to ArcGIS Engine Developing.NET Applications for ArcGIS Engine

35. Esri UC2013. Technical Workshop. Adding Functionality to Engine Leverage existing commands and tools provided with the Engine SDK - On a ToolbarControl - Programmatically Build your own components - Such as Commands, Tools, Extensions, Custom Layers, etc… - Specific to your Engine Application - Generic for all Engine applications - Work in both Engine and Desktop applications Developing.NET Applications for ArcGIS Engine

36. Esri UC2013. Technical Workshop. Using Geoprocessing in Engine Why use geoprocessing in Engine? - Why reinvent the wheel? - ArcGIS comes with hundreds of Geoprocessing tools - Developed by specialists in their field Provides a framework to author Model and Script tools in ArcGIS Desktop - Consume these tools in Engine Developing.NET Applications for ArcGIS Engine

37. Esri UC2013. Technical Workshop. Using Geoprocessing in Engine Using system tools Developing.NET Applications for ArcGIS Engine

38. Esri UC2013. Technical Workshop. Using Geoprocessing in Engine Using custom tools Developing.NET Applications for ArcGIS Engine

39. Esri UC2013. Technical Workshop. Background Geoprocessing in Engine Framework to allow Geoprocessing tools to execute in a separate process Great alternative to multi-threaded applications Allows User Interface to remain responsive while processing What is Background Geoprocessing Developing.NET Applications for ArcGIS Engine

40. Esri UC2013. Technical Workshop. Background Geoprocessing Execute tool using ExecuteAsync method on the Geoprocessor object Wire in the events - ToolExcuted - Must handle to know when tools complete - ProgressChanged - MessagesCreated - ToolExecuting Run system tools, models, and script tools What is Background Geoprocessing Developing.NET Applications for ArcGIS Engine

41. Esri UC2013. Technical Workshop. Geoprocessing in Engine demo Developing.NET Applications for ArcGIS Engine

42. Esri UC2013. Technical Workshop. Background Geoprocessing Tips: - Set OverwriteOutput = True - Tools require different license levels or extensions - Desktop help is your friend - Understand GP Messaging - Learn about the Result Object Tips for working with the Geoprocessor Developing.NET Applications for ArcGIS Engine

43. Esri UC2013. Technical Workshop. New Runtime for ArcGIS Developing.NET Applications for ArcGIS Engine

44. Esri UC2013. Technical Workshop. New Runtime for ArcGIS New Architecture Easy to Deploy Solutions - Software, maps and data 64 bit Native Support Modern API - WPF and Java Reduced Memory and Disk Footprint Developing.NET Applications for ArcGIS Engine

45. Esri UC2013. Technical Workshop. New Runtime for ArcGIS Not a functional equivalent to Engine Not an ArcObjects replacement New APIs - Code will need to be re-written - Should leverage general patterns for data sharing and distribution Developing.NET Applications for ArcGIS Engine

46. Esri UC2013. Technical Workshop. Please don’t forget to fill out the surveys Questions? Developing.NET Applications for ArcGIS Engine

47. Esri UC2013. Technical Workshop.Developing.NET Applications for ArcGIS Engine