Install packages

Choose a package

Browse NuGet or PyPI. Each entry lists its published identifier, checked version, registry link, and license. Install commands, dependencies, and requirements stay on the registry listing. For editor add-ons, browse Visual Studio Extensions or VS Code Extensions.

Check the package's required runtime and host application before installing it. A package manager installs files and dependencies; it does not supply an Alibre Design or MicroStation installation.

.NET libraries

Open a compatible .NET project and add the reference with the identifier and version from its catalog entry:

dotnet add package <PackageId> --version <Version>

Restore and build the project afterward. Consult the NuGet listing for namespaces, entry points, dependencies, and host integration.

The NuGet catalog marks library packages separately from tools.

.NET tools

Install the selected tool with its published identifier, then inspect the result:

dotnet tool install --global <PackageId> --version <Version>
dotnet tool list --global

Follow the NuGet listing for launch arguments and MCP client setup where applicable.

Python packages

Create a virtual environment and install the published package into it:

python -m venv .venv
.\.venv\Scripts\python.exe -m pip install <package>==<version>

The alibrex entry gives its checked version and registry link; the PyPI listing carries its requirements and usage.

Verify before using your own files

Confirm the installed version, then follow the package's smallest documented example. Use a sample or copy of a project while checking the integration. Keep the runtime, host application, and package versions together when reporting an issue.