I am trying to update the Dlubal api nuget package from 2.13.8 (2.3.2026) to latest 2.14.5 (4.5.2026) and I get an error that “Package Dlubal.Api 2.14.5 is not compatible with net8.0…Package Dlubal.Api 2.14.5 supports: net9.0…”. I see nothing about that in Api Releases notes on https://www.dlubal.com/en/products/dlubal-api/api-documentation/examples
Am I missing something? It seems unusually that a random weekly update would change runtime platform which is the base on which C# Apps using the api are built on.
You are not missing anything. This requirement was not clearly documented in the release notes, and we have corrected that.
Starting with Dlubal.Api 2.14.1, the C# NuGet package targets net9.0 instead of net8.0. The reason for this change was the integration of the GeoZone Tool client into the API package line.
As a consequence, Dlubal.Api 2.14.1 and newer, including 2.14.5, cannot be referenced from a project that still targets net8.0.
The current options are:
retarget the C# application to net9.0 and use Dlubal.Api 2.14.x
stay on Dlubal.Api 2.13.12 or earlier if the application must remain on net8.0
This affects only the C#/.NET client package. We agree that a runtime/platform change like this should have been highlighted explicitly, so we have added an “Action Required” note to the 2.14.1 release notes: https://apidocs.dlubal.com/release_notes.html#release-2-14-1
Thank you Tomas for the answer although this is quite frustrating from our side, since our developed internal solutions are now effectively blocked from updating to newer API versions without a framework migration. Changing .NET runtime availability across multiple company devices is also not a negligible issue. Also .net 8 is the current long support LTS release, while .net 9 is not and they have the same end date for support. Should we expect .net10 towards the end of year? Are there any plans to support both net8.0 and net9.0 packages going forward?
Hi @Bojan ,
we have used .Net9 as it was the base platform for our nuget package for Geo-Zone tool NuGet Gallery | Dlubal.API.GeoZoneTool 1.0.18.
I undersand that changes of the .Net versions are painful. We might consider multi platform approach for our nuget packages.
many structural engineers will use the API within Grasshopper for instance. However, Rhino/GH is using .Net 8. Meaning, calling API functions from GH can lead to exceptions being thrown (my case just now., so I cannot use some of the API functionalities)
Hi @Guillaume, @Bojan — good news, this is resolved as of 2.15.9.
The Dlubal.Api NuGet package is now multi-targeted and ships assemblies for net8.0, net9.0 and net10.0. Since Rhino/Grasshopper runs on .NET 8, the exceptions you were hitting should disappear once you update the package.
For context on what caused it: versions 2.14.1 through 2.15.8 targeted net9.0 only, so a .NET 8 host like Grasshopper was being asked to load a net9.0 assembly. If you pinned to 2.13.12 to stay on net8.0, you can now go straight to 2.15.9 without retargeting your project.
No configuration change is needed — NuGet resolves the matching assembly from your project's TargetFramework during restore, and existing net9.0 projects are unaffected.
If you're working against the older Rhino runtime on .NET Framework 4.8 instead, there's a separate Dlubal.Api.NetFramework package that also gained the GeoZone Tool dependency in this release.
Thanks for raising it — please shout if anything still misbehaves in Grasshopper.