User Tools

Site Tools


Deploying an application

Documentation | Deploying

Standard application

By default, TatukGIS contains all general-purpose layers and functionality built-in. That means it is not required to deploy any other library, and a DK developed application is self-contained.

  • Delphi
    just deploy the executable file. If the application is built with runtime packages, then the required .bpl file must also be deployed,
    • iOS & Android
      just compile the application,
  • .NET
    just deploy the executable file and TatukGIS library assembly (usually TatukGIS_DK11.dll),
    • ASP.NET
      just deploy the application and the TatukGIS library into bin/ folder,
  • JAVA
    just deploy the executable file and the TatukGIS library .jar (usually TatukGIS_DK11.jar),
  • ActiveX
    just deploy the executable file and register the TatukGIS library .ocx (usually TatukGIS_DK11.ocx); a side-by-side ocx is possible in Visual Studio.

3rd party libraries

It is sometimes required to deliver 3rd party libraries, like ECW, MrSID. SQLITE, etc.

On the Windows operating system, libraries can exist in 32bit and 64bit versions. As long as the application runs only in 32- or in 64- bits mode, libraries can be simply deployed to the same folder as an application.

  • iOS
    SQLite library provided for iOS is a universal (both 32- and 64- bit) library and should be deployed to the same folder as an application.
  • JAVA
    Use TGIS_Utils.SetLibrariesSearchPath method to define the search path for the library other than standard.
  • ActiveX
    Deployment must be relative to the folder with the TatukGIS .ocx file.

Things are a bit more complicated if the application is deployed as 32-bit and with 64-bit enabled (e.g. .NET app). Then libraries should be placed in an x86/ and x64/ subfolders. Then an application uses the proper version of the library depending on the mode of execution. Those folders can also be used in Delphi apps. For example, the TatukGIS Editor/Viewer has two executables: one for 32-bit and one 64-bit application. Both are deployed to a single folder with, x86/ and x64/ subfolders for 3rd party libraries.

Deployment libraries are located in an installation folder of the DK in a Deployment subfolder-folder. Some libraries (e.g. ECW, MrSID) require that developer that a developer will download libraries from the vendor on his own. Please, refer to readme file located in a particular library folder.

Be aware that some 3rd party libraries require a specific version of Microsoft Visual C++ Redistributable Package and the application setup procedure should ensure that a proper version is installed.

Grid shift files

Generally, all datums, projections etc., are included in the library. However, sometimes local grid shift files are required. Due to size, these files must be deployed individually.

Grid shift files, if required. should all be deployed to Datums subfolder (see also Grid Shifts Files).

Folders layout

The final application folder structure can be similar to:

    +-- x86
    +-- x64
    +-- Datums


  • app
    application folder
    • for Delphi, .NET, and Java applications, there is a folder with an application executable file;
    • for ASP.NET applications, it is a bin/ folder;
    • for ActiveX applications, it is the location of the TatukGIS ocx. file;
    • third party libraries can be placed here as long as they use the same target architecture (double-check your .NET application to use specific “Platform target” ).
  • x86
    folder with 32-bit specific libraries
    not applicable on iOS or Android,
  • x64
    folder with 64-bit specific libraries
    not applicable on iOS or Android,
  • Datums
    folder with grid shift files
2021/09/24 08:45

Page Tools