Skip to content

Commit 7113071

Browse files
committed
Review export doc
1 parent ec01403 commit 7113071

1 file changed

Lines changed: 12 additions & 10 deletions

File tree

  • content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/csharp/extensibility-api-howtos

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/csharp/extensibility-api-howtos/export-an-extension.md

Lines changed: 12 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -7,27 +7,29 @@ weight: 99
77

88
## Introduction
99

10-
This how-to describes how you can export an extension so that you can publish it in the Marketplace or directly share it with other Mendix developers.
10+
This how-to describes how to export an extension so you can publish it in the Marketplace or share it directly with other Mendix developers.
1111

1212
## Prerequisites
1313

14-
To be able to export extension add-on modules, you need to have the feature flag `--enable-extension-development` enabled. For more information, see [Get Started with the Extensibility API](/apidocs-mxsdk/apidocs/csharp-extensibility-api-11/get-started/).
14+
Before exporting an extension add-on module, ensure the following feature flag is enabled: `--enable-extension-development`
1515

16-
## Procedure
16+
For more information, see [Get Started with the Extensibility API](/apidocs-mxsdk/apidocs/csharp-extensibility-api-11/get-started/).
17+
18+
## Steps
1719

1820
1. In Studio Pro, open the app that contains your development extension.
19-
2. Create a new module with the same name as your extension folder. For example, if your extension folder is called 'MyFirstExtension', your module must also be called 'MyFirstExtension'.
20-
3. In **App Explorer**, go to **Settings** of this module and then go to the **Export** tab.
21+
2. Create a new module with the same name as your extension folder. For example, if your extension folder is named *MyFirstExtension*, your module must also be named *MyFirstExtension*.
22+
3. In the **App Explorer**, navigate to the **Settings** of this module and click the **Export** tab.
2123

2224
{{< figure src="/attachments/apidocs-mxsdk/apidocs/extensibility-api/extensibility-api-howtos/export-an-extension/export-tab.png" max-width=80% >}}
2325

24-
4. Set **Module type** to *Add-on module*.
26+
4. Set **Module type** to **Add-on module**.
2527
5. In the **Module version** field, enter the version number of the extension.
26-
6. In the **Extension Name** field, select the name of your extension. This must match with your module name.
28+
6. In the **Extension Name** field, select the name of your extension. This must match your module name.
2729

28-
{{% alert color="info" %}} If you do not set the **Extension name** field, your feature flag is not configured correctly. For more information, see [Get Started with the Extensibility API](/apidocs-mxsdk/apidocs/csharp-extensibility-api-11/get-started/). {{% /alert %}}
30+
{{% alert color="info" %}} If you do not see the **Extension name** field, your feature flag is not configured correctly. For more information, see [Get Started with the Extensibility API](/apidocs-mxsdk/apidocs/csharp-extensibility-api-11/get-started/). {{% /alert %}}
2931

3032
7. Click **OK** to save the settings.
31-
8. In **App Explorer**, right-click the module and click **Export** to export the extension.
33+
8. In the **App Explorer**, right-click the module and click **Export** to export the extension.
3234

33-
Now you can [publish the extension in the Marketplace](/appstore/submit-content/#adding) or directly share it with other Mendix developers.
35+
Now you can [publish the extension in the Marketplace](/appstore/submit-content/#adding) or share it with other Mendix developers.

0 commit comments

Comments
 (0)