How to convert a Composer bot from v1.x to v2.x

  • Article

APPLIES TO: Composer v2.x

When you open a bot built with Composer 1.4 or earlier in Composer 2.0 or later, Composer can automatically copy and convert your bot to the use the new bot runtime. The new bot will use the new runtime and have access to Composer's latest features.

Starting with version 2.0, Composer creates bots that use the adaptive runtime. The adaptive runtime supports new ways to extend Composer and bots, including support for speech, mutli-language scenarios, and Microsoft Teams support. It also has extension points for dynamically adding new components for your bot.

In Composer versions 1.4 and earlier, bots used an older runtime implementation.

Prerequisites

  • An existing bot built in Composer 1.4 or earlier.
  • Composer 2.0 or later. See Install Composer for instructions.

Convert to the new runtime

  1. Open Composer and open your existing bot project.
  2. Composer asks if you want to convert your project to the latest format. Select Convert. During conversion, Composer will create a copy of your bot and convert it to use the new runtime. Your original bot won't be changed.
  3. In the Create a bot project window:
    1. Provide a name for the converted bot project.
    2. Select the runtime type and the runtime language for the converted bot.
    3. Select a location in which to create the new project.
    4. Select Create to have Composer create the new project. This step can take a few moments.

When it's done, Composer opens the new project.

  • If your original bot used no custom actions, you're ready to use your new bot!
  • If your original bot used any custom actions, the custom actions are deactivated in your new bot. To migrate your custom actions, continue with the next section.

Migrate your custom actions

These steps are required only for bots that used custom actions, which Composer deactivates when it converts from the earlier bot format.

If your converted bot contains deactivated actions, Composer will display an error sign in the upper right. To find your deactivated custom actions:

  1. Select the error sign. Composer displays a list of the deactivated actions in the Problems pane.
  2. To show a deactivated action on the authoring canvas, select the location associated with the action in the list.
  3. Determine how you want to address each such action.
    • This version of Composer might provide some of the capabilities your custom actions originally provided, such as support for speech, multiple languages, and Microsoft Teams. For more about new capabilities in Composer, see What's new.
    • Component packages are a way to add features to Composer. An existing component might provide some of the capabilities your custom actions provided. For information about components, see Understanding packages.
    • If Composer or a component package doesn't provide the capabilities your bot needs, you can convert one or more custom actions into components. For more information, see how to Create custom actions and Create and share packages.