Skip to main content

Install on Windows

MapCore ships for Windows as a single installer, MapCoreSetup.exe. A debug build is published alongside it as MapCoreSetup_Debug.exe; install that one only if you need to debug into MapCore itself, and note that it installs to its own directory so you can have both.

Prerequisites​

The installer checks for two things and offers to install each if it is missing, so in the normal case there is nothing to do in advance:

  • Visual C++ 2015–2022 Redistributable (x64). Required. If you decline, setup exits.
  • DirectX runtime (the June 2010 redistributable). Required for the Direct3D rendering systems.

Beyond that you need a 64-bit Windows machine and a GPU with working drivers. MapCore can render through Direct3D 9, 9Ex, 11, or OpenGL — you choose at runtime, not at install time.

Install​

MapCore 12.5.0. Downloads are credential-gated by Artifactory itself — the first one opens its sign-in page.

Downloads are not available on this network. Ask your administrator where to obtain MapCore releases.

MapCore SDK installer

Installs the libraries, headers and the sample tools

Map Layer Server installer

The server, its web GUI, and optional Windows Service registration

Run the installer and pick the components you want:

ComponentContains
SDKHeaders, libraries, documentation and examples — this is what you build against
MCTesterThe interactive test application, and the fastest way to confirm the install works
MCVectorEditorVector data editor
MapProductionToolMap production and data conversion
McObjectSchemeConverterObject scheme conversion

Choosing Full installation selects all of them.

The default location is versioned:

C:\Program Files\MapCore7\<version>

Installing a new version therefore does not disturb an existing one, which matters when you are migrating a project and want both available.

What you get​

C:\Program Files\MapCore7\<version>\
├── SDK\
│ ├── Include\ headers — the include path for your project
│ ├── Bin\Dll\ runtime DLLs
│ ├── Bin\Lib\ import libraries to link against
│ ├── Bin\Pdb\ debug symbols
│ ├── Config\ plugins.cfg, plugins_min.cfg, resources.cfg, fxplugin.cfg, media
│ ├── Licenses\ third-party attribution notices, to redistribute with the binaries
│ └── Examples\
│ ├── WPF\ C# / WPF example
│ ├── WinForms\ C# / WinForms example
│ ├── CPP-MFC\ C++ / MFC example
│ └── MCTester\ source of the test application
└── Tools\ the tools you selected, plus their media and symbology standards

Two of these matter more than the rest when you first build:

  • SDK\Config holds plugins.cfg, plugins_min.cfg, resources.cfg and fxplugin.cfg. MapCore reads them at device creation, from the directory named by SInitParams::strConfigFilesDirectory — or the current working directory if you leave that empty. Getting this wrong is the most common cause of a device that fails to create on a machine where it worked before.
  • SDK\Bin\Dll must be on the PATH, or its DLLs must sit beside your executable.

Verify​

Run MCTester from the Start menu. It creates a device, a viewport and a terrain exactly as your own code will, so if it draws a map your installation and your GPU drivers are both fine. If it does not, the log it leaves — MapCore.log, in the working directory — names the reason, and that is a much shorter path to a diagnosis than debugging your own first integration.

Set up a project​

For a C++ project:

  1. Add SDK\Include to the include path.
  2. Link against the .lib files in SDK\Bin\Lib that you use.
  3. Make SDK\Bin\Dll reachable at run time.
  4. Point SInitParams::strConfigFilesDirectory at SDK\Config, or copy its contents next to your executable.

For C#, the WPF and WinForms examples under SDK\Examples are working projects with the references already set — starting from one of those is faster than assembling it yourself.

Next steps​

  • Quickstart — device, viewport, layer, camera, in about thirty lines
  • Architecture — what those objects are and how they relate
  • Read data over HTTPS — the CA bundle that certificate-verifying requests need

Verified against MapCore 12.5.0

Written from packaging/windows/inno-setup-mapcore.iss, packaging/windows/prereqs.iss