For up-to-date product documentation, see the IBM MobileFirst Foundation Developer Center.


Registering Windows applications from the MobileFirst Platform CLI

We can use the IBM MobileFirstâ„¢ Platform Command Line Interface (CLI) to register your Windows application to an instance MobileFirst Server.


Before you begin


Overview

Once you have the client side of your Windows application initially defined, you can prepare for further development tasks by registering it to a MobileFirst Server.

Registration occurs for only the app that corresponds to the current working directory in which you run the mfpdev app register command. If the current working directory is a Windows 8.1 Universal project that contains both Windows 8.1 desktop and Windows Phone 8.1 then both the desktop and Windows Phone projects are registered. If the current working directory is the Windows or WindowsPhone directory under the Windows 8.1 Universal project, or one of their subdirectories, then registration occurs for only the project that corresponds to the directory that you are in.


Procedure

  1. Check that the target MobileFirst Server is up and running.
  2. Navigate to the directory that contains your app, or one of its subdirectories.
  3. Register your app to the server. Use one of the following procedures:
    • To register the app to the default server, run the following command:

      mfpdev app register

      Note: If you have not previously set a default server and a MobileFirst Server is running on the local system, this command registers the app to the local MobileFirst Server, and this server is made the default.

    • To register your app to a server that is not the default server:
      1. Create a server profile by running the mfpdev server add command. For example:

        mfpdev server add Server1 -url https://company.mobile.com:9080 -login admin -password secretPassword! For more information about the mfpdev server add command, run mfpdev help server add.

      2. To register your app to the server that you just defined, run the mfpdev app register command, and specify the server profile that you just created. For example:

        mfpdev app register Server1

    For more information about this command, including optional parameters, run mfpdev help app register.


Results

The app is registered to the target server. Data about the app that is obtained from its platform properties file (.appxmanifest) such as application name, version number, and app ID is sent to the server. If the root client properties file (mfpclient.resw) for each registered Windows platform exists, it is updated with the value of the server's URL. If the file did not exist, a mfpclient.resw file is created that includes the server's URL. The client properties files are located as follows, depending on your specific Windows platform:

For Windows 8.1 Universal projects, two client properties files are created or updated:


What to do next

If the mfpclient.resw file was created when you ran mfpdev app register, then the file is not linked into the Windows project in your IDE and you need to link it. If the mfpclient.resw was created by using NuGet, then the file is already linked into the project, but you need to update the properties in the file to correspond to our target MobileFirst Server. For more information, see Client property file for Windows 10 Universal Windows Platform and Windows 8 Universal.

We can proceed with other development tasks that depend on the MobileFirst Server. For example, we can preview your app, test your app's security features, and manage your app from the MobileFirst Operations Console.

Parent topic: Registering Windows applications to MobileFirst Server