How to: Move from the former starter

A delivery is still started by the former starter (StarterPro) with its StarterPro.config.xml, and it should move to this starter without typing the configuration again.

The command /import-starterpro reads the former configuration and writes a project file of format 2 (bootstrapper.json). It lists, one line each, what it did not take over and what needs a hand. The project file is then checked with /check and, if needed, finished in Bootstrapper Manager (see its „WKL Bootstrapper Manager user guide“) or in a text editor.

1. Copy Wkl.Bootstrapper.exe into the folder of the former configuration, or name the configuration with its path.

2. Convert it:

   Wkl.Bootstrapper.exe /import-starterpro "\\server\amed\deploy\StarterPro.config.xml"

   The project goes to bootstrapper.json beside the configuration; /out <file> names another file. An existing file is never overwritten: the command then ends with code 11.

3. Work through the listed lines (see Remarks), then check the result:

   Wkl.Bootstrapper.exe /check "\\server\amed\deploy\bootstrapper.json"

4. Deliver the starter with the new project file as described in How to: Deliver an application with the bootstrapper.

• Not taken over: the SQL connection (SRV, CURUSR, CATALOG) and the password, which the former starter kept base64-encoded and so readable by anyone. The lines name them, never their values. An application keeps its connection itself, for example with WKL Linked Tables Manager.
• INI values whose key looks like a secret (pass, pwd, kennwort, secret, token, ending in key) are left out for the same reason; the starter refuses them in a project.
• CLIENTPATH is not used: each version goes into its own folder in the user's profile, so a new version never overwrites the running one.
• A file outside SERVERPATH is left out: every file must come from the delivery.
• A registered file (registerCom, registerNetCom) needs its registration.json beside it in the delivery; it is written with tools\Export-ComRegistration.ps1 on the publisher's computer.
• The logo is named by its file name: copy it beside the starter.
• The product key is made from the company name (letters, digits, ., -, _). It names the entry under Apps and the user's folder; choose it before the first delivery and keep it.
• A company version that is no version of two to four numbers becomes 1.0.0 and is listed.

• The project file (format 2) - every member of the project file.
• The installer of the bootstrapper 2.0 - /import-starterpro, /check and the other commands.
• How to: Publish a signed delivery - signing the deliveries of the moved application.