Skip to content

Commit 9f027b6

Browse files
committed
Get started
1 parent fbd9038 commit 9f027b6

1 file changed

Lines changed: 13 additions & 17 deletions

File tree

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

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-10/extensibility-api/csharp/get-started.md

Lines changed: 13 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -7,39 +7,35 @@ weight: 2
77

88
## Introduction
99

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.
1111

1212
## Development Setup
1313

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-
2214
{{% alert color="info" %}}
2315
Extensions can be built on any operating system as the underlying framework is cross-platform.
2416
{{% /alert %}}
2517

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+
2622
## Using Extensibility API via a Hosted NuGet Package
2723

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.
2925

3026
{{% 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.
3127
{{% /alert %}}
3228

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**
3430

3531
## Importing Extensibility API via a NuGet Package Hosted on a Local Repository
3632

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.
3834

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:
4036

4137
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.
4339
3. Drop the package into the local folder.
4440
4. Refresh the NuGet manager to see the package alongside the other packages.
4541

@@ -53,13 +49,13 @@ For more information on local NuGet repositories, see the official [Local Feeds]
5349

5450
## Extensions Development Setup
5551

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.
5753

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.
5955

6056
Studio Pro will load your extension, only if it complies with the following rules:
6157

62-
* Your extension needs to provide a manifest.json file.
58+
* Your extension needs to provide a `manifest.json` file.
6359
* This manifest file must contain a list of entry points for your extension. For example:
6460

6561
```

0 commit comments

Comments
 (0)