Setup

License

The NeoMAD license control is based on two main pieces of information: the client ID and the license key:

  • The client ID represents a customer - company or indie - who has signed a license contract with Neomades; no client ID is required to run the Starter version of NeoMAD
  • A license key is used to unlock an installation of NeoMAD on a given computer; each license key is bound to a client ID

Note

You need an internet connection to activate and check periodically the license.

Enter the Client ID (Indie and Business versions)

The first time it is used, NeoMAD asks for a client ID (unless you are using the Starter version). It will then connect to the Neomades server to check if this client ID is valid.

Enter the license key

Once the client ID has been validated, NeoMAD asks for a license key. It will then connect to the Neomades server to check if this license is valid and not already used.

When all these pieces of information have been validated by the Neomades server, your NeoMAD installation is ready to use.

Note

The license validity will then be checked periodically. An internet connection is required each time NeoMAD has to connect to the server to check the license validity (4 days for the Starter version, one month for the Indie and Business versions).

NeoMAD configuration file

The configuration of NeoMAD is stored in the neomad.properties file which can be located at three different places :

  1. In the NeoMAD’s project directory beside the NeoMAD URS file.
    This file must be created by the user using the neomad.properties.template file from NeoMAD’s installation directory.
  2. In the NeoMAD’s installation directory.
    This file is created during the installation of NeoMAD and is filled using the values you chose during the installation process or with the NeoMAD plugin settings.
    It can be manually edited later with a text editor or directly with the plugin. if the configuration must be updated.
  3. In the user home directory, inside a required .neomad directory:
    This file must be created by the user using the neomad.properties.template file from NeoMAD’s installation directory.
    • On Mac OS: /Users/username/.neomad/neomad.properties
    • On Windows: C:\Users\username\.neomad\neomad.properties

Note

Properties can be overridden in the command line see Neomad command line configuration properties.

These files and command line properties respect a priority order to select the needed property from prior to minor:

  1. Command line properties (see Neomad command line configuration properties)
  2. neomad.properties located in NeoMAD’s project
  3. neomad.properties located in NeoMAD’s installation directory
  4. neomad.properties located in user home directory

Note

e.g.
If the same property is set in the neomad.properties located in NeoMAD’s project and in the neomad.properties located in user home directory.
The property from the project folder will be selected.

Proxy

If you are connecting through a proxy, you will have to provide additional information in the neomad.properties file so that NeoMAD can connect to the Neomades server.

e.g.

PROXY_HOST=192.168.0.1
PROXY_PORT=1234
PROXY_USERNAME=john.doe
PROXY_PASSWORD=P@ssw0rd
PROXY_TYPE=HTTP

Android

The path to the Android SDK must be provided in the ANDROIDPATH property.

e.g.

ANDROIDPATH=C:/Program Files (x86)/Android/android-sdk (Windows)
ANDROIDPATH=/Applications/Android/android-sdk (Mac OS)

iOS (Mac OS only)

In a Mac OS environment, NeoMAD will automatically search for the SDK embedded in Xcode to build for iOS. Consequently, be sure that Xcode is installed in the environment where NeoMAD runs.

However you can override the default Xcode path to select another Xcode for compiling your NeoMAD project in the XCODE_PATH property.

e.g.

XCODE_PATH=/Applications/Xcode-beta.app

Note

In a Windows environment, since Xcode is not available, the project cannot be built. However the Xcode project can be generated and transferred to a Mac.

Windows Phone and Windows Store apps (Windows only)

The path of MSBuild must be provided in the MSBUILD_FRAMEWORK_PATH and MSBUILD_TOOLS_PATH properties:

  • MSBUILD_FRAMEWORK_PATH is used when targeting Windows Phone or Windows 8.0
  • MSBUILD_TOOLS_PATH is used when targeting Windows 8.1; this is possible only if the executing platform is Windows 8.1 and Visual Studio Express 2013 for Windows is installed

e.g.

MSBUILD_FRAMEWORK_PATH=C:/Windows/Microsoft.NET/Framework/v4.0.30319
MSBUILD_TOOLS_PATH=C:/Program Files (x86)/MSBuild/12.0/Bin

Note

In a Mac OS environment, since Visual Studio is not available, the project cannot be built. However the Visual Studio project can be generated and transferred to a PC.