StruXllence Community - All Forums

StaadPro.Interop NuGet: install, connect and choose the right preview

Mon, 02 Nov 2026 09:54:08 +0000

Installing StaadPro.Interop from NuGet: requirements, first connection and version checks

This thread covers consuming StaadPro.Interop in an application. It complements the repository overview, which focuses on architecture, source builds and contributions.

Package: StaadPro.Interop on NuGet
Verified public version, checked 2 November 2026: 1.0.0-preview.20261102.1
Current repository: StruXllence/StaadPro.Interop

1. What is installed?

StaadPro.Interop is a strongly typed managed wrapper for STAAD.Pro's OpenSTAAD interface. The verified public archive contains the net481 assembly, XML documentation and accompanying guides. Its metadata declares Newtonsoft.Json 13.0.3 as a dependency. NuGet normally restores the dependency automatically.

The package does not install STAAD.Pro, supply a Bentley license or replace the native structural-analysis engine. Installing the DLL successfully does not establish that an OpenSTAAD session is available or that a particular native operation is supported by the installed STAAD build.

2. Requirements before running the sample

Windows and a project targeting .NET Framework 4.8.1 (net481), with the appropriate targeting tools.
A separately installed and licensed STAAD.Pro application exposing the required OpenSTAAD APIs.
An open, controlled model for the initial connection check.
An STA entry point or an existing STA application thread, with coordinated/serialized access to the connected session.

The main package's target framework is net481. A recent .NET SDK does not make a net8.0 application compatible with that asset. The separately named Core.Testing preview has a different purpose; do not substitute it silently or reference both packages as if they were independent assemblies.

3. Install an exact public version

For a suitable existing project:

Code:
dotnet add YourApp.csproj package StaadPro.Interop --version 1.0.0-preview.20261102.1 --source https://api.nuget.org/v3/index.json
dotnet restore YourApp.csproj
dotnet build YourApp.csproj -c Release

The relevant project settings are:

Code:

  net481

In Visual Studio, open Manage NuGet Packages, select nuget.org, enable Include prerelease, search for StaadPro.Interop and choose the exact version. In Package Manager Console:

Code:
Install-Package StaadPro.Interop -Version 1.0.0-preview.20261102.1 -Source https://api.nuget.org/v3/index.json

Pinning a preview version makes a build reproducible. Check the release notes before upgrading, then rebuild and restart the consuming application so it actually loads the new DLL.

4. First connection: read the model path

Code:
using System;
using StaadPro.Interop.Services;

internal static class Program
{
    [STAThread]
    private static void Main()
    {
        using (var wrapper = OpenStaadWrapperProvider.GetRunning())
        {
            if (wrapper == null)
            {
                Console.WriteLine("No usable running OpenSTAAD session was found.");
                return;
            }

            Console.WriteLine(wrapper.Root.GetStaadFileFullPath());
        }
    }
}

Start with read-only queries, confirm the connected model and make units explicit. Use the selected version's IntelliSense and guides for Geometry, Load, Property, Output and the other adapters. Keep StaadPro.Interop.xml beside the DLL if copying assemblies outside the normal NuGet restore process.

5. How to distinguish a public release from a prepared archive

The public feed can be checked directly:

Code:
$feed = Invoke-RestMethod 'https://api.nuget.org/v3-flatcontainer/staadpro.interop/index.json'
$feed.versions

At the time of this post, the latest listed public version is 1.0.0-preview.20261102.1. This exact version is listed in the feed and its archive was downloaded for the checks behind this post. For future releases, do not treat a local archive, README or package-cache entry as proof that a version is downloadable from nuget.org.

For troubleshooting a feed issue, restore into a fresh package-cache directory with an explicit NuGet.Config containing the intended source. Avoid changing package IDs merely because a version has not been published.

6. Common problems and what to check

Package not found: verify the exact package ID, prerelease version and configured source. Enable prerelease packages in Visual Studio.
Framework incompatibility: inspect TargetFramework; the package's net481 target and the installed SDK are different requirements.
No running session: open licensed STAAD.Pro and a usable model, and verify that the application can access that session in the correct Windows context.
Unexpected native return value: record the exact STAAD build, method and arguments. Native contracts can differ across versions; do not convert every nonempty result into success.
Wrong numbers: check model identity, active/load-case selection, result availability, coordinate systems, signs and units before drawing an engineering conclusion.
Old behavior after upgrade: rebuild, restart and inspect the loaded DLL/package version rather than relying only on the package-manager UI.

7. Preview scope, licensing and responsible use

This is a preview. Managed tests and documented examples do not certify all live COM behavior or engineering acceptance. Native model changes can have partial effects; save a separate controlled copy before trying mutation workflows, and do not assume that disposing a wrapper saves or closes STAAD.Pro.

The downloaded 1.0.0-preview.20261102.1 archive declares Apache License 2.0 and StruXllence copyright in its NuGet metadata, and retains a notice for MIT-origin code. Earlier public versions, including 1.0.0-preview.20261028.4, shipped under their original terms. Follow the notices shipped with your exact package or source revision rather than assuming that current main-branch metadata describes every older release.

StaadPro.Interop is independent of Bentley Systems and is not an officially endorsed Bentley SDK. Bentley software and licensing remain separate.

For a package defect, open a reproducible GitHub issue with versions and a minimal nonconfidential example. For workflow questions, continue the discussion here and describe the engineering checks you need.

StaadPro.Interop repository: typed C# automation for STAAD.Pro

Mon, 02 Nov 2026 09:54:08 +0000

StaadPro.Interop: a C# foundation for repeatable STAAD.Pro automation

StaadPro.Interop is an independent, open-source .NET wrapper around Bentley STAAD.Pro's OpenSTAAD automation interface. The project is authored by Srinivasa Rao Masanam and is now published under StruXllence. Its purpose is to help engineers build maintainable C# applications around STAAD models using typed interfaces, structural entities, documented contracts and managed results.

Repository: github.com/StruXllence/StaadPro.Interop
Documentation: API reference | Installation and session lifecycle | Release notes

1. Why use a typed wrapper?

OpenSTAAD lets external programs interact with STAAD.Pro. In a larger engineering application, the difficult work extends beyond calling an automation method: identifying the correct running model, distinguishing IDs from array indices, interpreting native return values, preserving units and axes, handling incomplete native output, and coordinating operations on a shared COM session.

StaadPro.Interop provides a managed layer for those responsibilities. It exposes separate adapters and interfaces for related API areas, together with documented input and output models. This can make automation easier to discover in IntelliSense, review in code and exercise with repeatable tests. It does not replace STAAD.Pro's analysis engine or turn an unverified calculation into an accepted engineering result.

2. Main areas of the API

Connection and Root: acquire an existing STAAD session, inspect model identity and units, and explicitly request model/application operations.
Geometry: work with nodes, beams, plates, connectivity and groups. Read the method contracts before using creation, merge or mesh operations.
Load: inspect primary/reference/combination cases, assignments and metadata, and build selected load-definition workflows.
Property: inspect materials, member sections and specifications, with version-aware contracts and separately acquired catalog capabilities where applicable.
Output: retrieve supported analysis/design observations through named managed results. Check result status before consuming data, and verify axes, signs and units.
Support, Commands and Design: support definitions/assignments, analysis-command configuration and supported design-brief/query workflows.
Table and View: supported report-table operations and graphical orientation requests. Coverage is evolving; use the exact version's documentation rather than assuming every OpenSTAAD operation is implemented.

3. Runtime requirements

Live interoperability requires Windows, a consumer targeting .NET Framework 4.8.1, and a separately installed/licensed STAAD.Pro version exposing the APIs being used. The .NET SDK used to build a project is not the same thing as its target framework. This main package should not be treated as a general .NET 8 or cross-platform library.

An open model and an appropriate COM apartment are required for model operations. Keep acquisition and subsequent calls on the application's established STA thread; serialize access to the same STAAD session. Moving calls to Task.Run does not automatically make COM access safe.

4. A small read-only starting point

With an appropriate package/project reference in a Windows net481 console application, open a STAAD model and start by reading its identity:

Code:
using System;
using StaadPro.Interop.Services;

internal static class Program
{
    [STAThread]
    private static void Main()
    {
        using (var wrapper = OpenStaadWrapperProvider.GetRunning())
        {
            if (wrapper == null)
            {
                Console.WriteLine("Open a usable STAAD.Pro session first.");
                return;
            }

            Console.WriteLine(wrapper.Root.GetStaadFileFullPath());
        }
    }
}

Confirm the returned model before adding geometry or result queries. Acquiring an instance is not proof that an analysis has completed or that its results are current. Saving, closing, reloading and analyzing models remain explicit operations with potential side effects.

5. Build from source and contribute

Code:
git clone https://github.com/StruXllence/StaadPro.Interop.git
cd StaadPro.Interop
dotnet build StaadPro.Interop.sln -c Release
dotnet test tests/StaadPro.Interop.Tests/StaadPro.Interop.Tests.csproj -c Release --no-build

Use a suitable Windows development environment and the repository's current setup instructions. Offline managed tests can run without Bentley binaries; live integration work needs licensed STAAD.Pro. Managed test coverage and packaged XML examples are evidence about the wrapper, not certification of every native STAAD build or engineering convention.

Useful contributions include minimal reproducible issues, clearer method contracts, controlled examples and regression tests. For a defect, report the package version or source commit, STAAD version, target framework, exact method, units, expected result and observed result. Use a small nonconfidential model where possible. Do not upload client/project files without permission.

6. Source versus published package

The main branch can contain work that is not yet available on NuGet. As checked on 2 November 2026, 1.0.0-preview.20261102.1 is listed in the public package feed and its archive is downloadable. The main branch can still move ahead of a published release. Pin the exact version or commit when reproducing a workflow. The companion NuGet thread explains installation of the verified public release.

License and independence

The current repository declares Apache License 2.0 and includes attribution/legacy notices. Earlier published archives retain the terms shipped with those archives; consult the exact revision and package notices. This is an independent project, not a Bentley-endorsed or Bentley-supported product. STAAD.Pro/OpenSTAAD and other referenced names belong to their respective owners, and no Bentley license or proprietary binaries are included.

Discussion: Which repeated engineering task would you like to automate first: geometry checking, load auditing, result extraction or reporting? Describe the workflow and the checks you would need before relying on it.