You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/apidocs-mxsdk/apidocs/studio-pro-10/extensibility-api/csharp/get-started.md
+13-17Lines changed: 13 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,39 +7,35 @@ weight: 2
7
7
8
8
## Introduction
9
9
10
-
This document helps you set up a basic development environment for building extensions. Additionally, you can find links here to additional tutorials that help familiarize you to the extensibility API topics.
10
+
This document describes how to set up a basic development environment for building extensions.
11
11
12
12
## Development Setup
13
13
14
-
The recommended development environment is [Visual Studio 2022](https://visualstudio.microsoft.com/) running on Windows. This documentation is centered on this setup. (You can also use other IDEs and other .NET compatible programming languages like [F#](https://fsharp.org/)).
15
-
16
-
Install the latest Studio Pro version from the Mendix [Marketplace](https://marketplace.mendix.com/link/studiopro/).
17
-
18
-
{{% alert color="info" %}}
19
-
Make sure to keep this Studio Pro installation up-to-date to benefit from new features and fixes.
20
-
{{% /alert %}}
21
-
22
14
{{% alert color="info" %}}
23
15
Extensions can be built on any operating system as the underlying framework is cross-platform.
24
16
{{% /alert %}}
25
17
18
+
The recommended development environment is [Visual Studio 2022](https://visualstudio.microsoft.com/) running on Windows. This documentation is centered on this setup. You can also use other IDEs and other .NET compatible programming languages like [F#](https://fsharp.org/).
19
+
20
+
Install the latest Studio Pro version from the Mendix [Marketplace](https://marketplace.mendix.com/link/studiopro/). Make sure to keep this Studio Pro installation up-to-date to benefit from new features and fixes.
21
+
26
22
## Using Extensibility API via a Hosted NuGet Package
27
23
28
-
You can start extension development by simply including the `Mendix.StudioPro.ExtensionsAPI` NuGet package to your project by searching for *Mendix.Studio.ExtensionsAPI* in NuGet.
24
+
Start extension development by including the `Mendix.StudioPro.ExtensionsAPI` NuGet package to your project by searching for *Mendix.Studio.ExtensionsAPI* in NuGet.
29
25
30
26
{{% alert color="warning" %}}The initial released package version compatible with Mendix 10.12.0 was 10.12.38909. This has been updated to 10.12.0+38909 to match the Studio Pro version.
31
27
{{% /alert %}}
32
28
33
-
Depending on your local environment setup, you possibly need to manually add a NuGet package to your solution. You can add a package source to Visual Studio via the menu:**Tools** > **Options** > **NuGet Package Manager** > **Package Sources**
29
+
Depending on your local environment setup, you may need to manually add a NuGet package to your solution. You can add a package source to Visual Studio via the menu by clicking**Tools** > **Options** > **NuGet Package Manager** > **Package Sources**
34
30
35
31
## Importing Extensibility API via a NuGet Package Hosted on a Local Repository
36
32
37
-
Another option to start extension development is to import a locally hosted `Mendix.StudioPro.ExtensionsAPI` NuGet package into your project.
33
+
Another way to start extension development is to import a locally hosted `Mendix.StudioPro.ExtensionsAPI` NuGet package into your project.
38
34
39
-
To create a local NuGet repository that will let you host and use NuGet packages shared with you, follow the procedure below:
35
+
To create a local NuGet repository that will let you host and use NuGet packages shared with you, follow the steps below:
40
36
41
37
1. Go to **Tools** > **Options** > **NuGet Package Manager** > **Package Sources**.
42
-
2.Press the green plus sign and specify a local folder, instead of a network location.
38
+
2.PClick the green plus sign and specify a local folder, instead of a network location.
43
39
3. Drop the package into the local folder.
44
40
4. Refresh the NuGet manager to see the package alongside the other packages.
45
41
@@ -53,13 +49,13 @@ For more information on local NuGet repositories, see the official [Local Feeds]
53
49
54
50
## Extensions Development Setup
55
51
56
-
Extensions load from within your mendix application and will only be loaded while the app is open.
52
+
Extensions load from within your Mendix application and will only be loaded while the app is open.
57
53
58
-
If you specify the `--enable-extension-development` flag you can debug your extension by placing it into a new subfolder within your app directory. The format of the folder must be `<Mendix app folder>\extensions\<your extension name>` where all extensions that you want to load must exist inside the <`Mendix app folder>\extensions` subfolder.
54
+
If you specify the `--enable-extension-development` flag, you can debug your extension by placing it into a new subfolder within your app directory. The format of the folder must be `<Mendix app folder>\extensions\<your extension name>` where all extensions that you want to load must exist inside the <`Mendix app folder>\extensions` subfolder.
59
55
60
56
Studio Pro will load your extension, only if it complies with the following rules:
61
57
62
-
* Your extension needs to provide a manifest.json file.
58
+
* Your extension needs to provide a `manifest.json` file.
63
59
* This manifest file must contain a list of entry points for your extension. For example:
0 commit comments