SpinFire Publish 2025.2.0 Release Notes
Overview
SpinFire Publish 2025.2.0 updates importers and fixes a number of bugs. (NB: Starting with the previous version, 2025.1.0, ArangoDB is no longer supported as a database for Publish customers).
Assembly Version |
2025.2.02904.20011 |
Latest supported ArangoDB version |
⚠️ No longer supported |
Earliest supported ArangoDB version |
⚠️ No longer supported |
Attention
SpinFire Publish (formerly Centro CAD Publisher) customers MUST use a one-time app to migrate from the 3rd-party-managed database (ArangoDB) to an app-managed database (SQLite). Click here for more info.
New Features and Improvements
Simplified installation procedure for upgrades
Remove requirement for ArangoDB from Centro SDK
appSettings.jsonc is now supported for SDK configuration
Importer updates:
NX
Up to NX2506
Creo
Up to 12
Parasolid
Up to 38
Navisworks
Up to 2026
Autodesk Inventor
Up to 2025
CATIA V5
Up to 2025
3DXML
Up to 2025
Inventor
Up to 2026
Bug Fixes
Pipeline job processing loop is not robust enough and can prevent any processing after a fault
Installation fails when CENTRO_CONFIG_DIR env var exists but points to an non-existent directory
Centro installers do not fail when they can’t replace DLLs during upgrade
Two error alerts constantly show when deploying Pipeline
Web app writes log in wrong folder when receiving WCF call before start
Web API docs page fails to load
Catalog Request Pipeline is still created and it’s possible to deployed it for Publish in specific case
Remove extra call to DB when registering Pipeline as previously deployed
Loading pipelines sends roundtrip to DB for each non-deployed pipeline
Remove duplicate DB call to fetch auth ticket when deploying Pipeline
Email sender fails to instantiate when ‘MailUsername’ is set but is not a valid email address
Incorrect error message is displayed when a user tries to deploy pipeline with incorrect email action
Reference on Core.Standard.dll is missed in some SDK examples
Note
SDK Users:
Visual Studio Projects using the Centro SDK must now target .NET Framework 4.8.1 minimum and turn on automatic binding redirects.
Supported Environments
Centro Web / File Server Environment |
Minimum |
Recommended |
Optimum |
Operating System |
Windows Server 2016-2025 (64-bit) Windows 10/11 (64-bit) |
Windows Server 2016-2025 (64-bit) |
Windows Server 2016-2025 (64-bit) |
CPU/Processor * |
Intel i7 8 Core 4 GHz (or equivalent) |
Intel i7 8 Core 4 GHz (or equivalent) |
|
Memory |
16 GB |
64 GB |
128 GB |
Disk Space † |
10 GB free |
50 GB free |
100 GB free |
It’s recommended to have n+1 core processors where n is the number of total concurrent jobs running.
† The amount of available free space is dependent on the amount and size of files and revisions uploaded as resources to the Catalog.
Client Environment |
Minimum |
Recommended |
Optimum |
Browser |
WebGL Compatible Browser
|
Chrome FireFox Edge |
Chrome / Edge |
Memory |
2 GB |
4 GB |
8 GB |
Prerequisite Installations
Microsoft .NET Framework 4.8.1Internet Information Services (IIS)