Supported architecture by product generation
| Line | Application stack | UI/reporting | Data/integration | Deployment constraints |
|---|---|---|---|---|
| VisualBase 12 (Pre-release) | .NET 10; ASP.NET Core; Blazor WebAssembly/server; YARP 2.3.0 | DevExpress 25.2.7; Crystal Reports runs in a separate .NET Framework 4.8 component | SQL Server; REST; OIDC; service-based topology | Windows installation package; ASP.NET Core 10 hosting bundle required; full browser-journey and production gateway/load-balancer testing not yet complete |
| VisualBase 11 (Beta) | .NET 8; ASP.NET Core; Blazor WebAssembly/server; modular services | DevExpress 25.2.7; BI, report and dashboard services; Crystal Reports interoperability | SQL Server; EF Core/Dapper; OIDC/Microsoft 365; YARP; centralized logging | Beta; interfaces and packages may change; no general-availability service level; one standard-port installation at a time on a host |
| VisualBase 10 | ASP.NET Web Forms on .NET Framework 4.8.1; desktop components on earlier .NET Framework versions | DevExpress 25.2.7; SAP Crystal Reports 13.0.4000 | SQL Server; ASP.NET Identity/Owin; Windows services and integrations | Windows Server/IIS required; not container-native; Crystal Reports and desktop components are Windows-specific; upgrades require regression testing of customer reports and custom code |
| VisualBase 8–9 | ASP.NET Web Forms on .NET Framework 4.6.2; Windows desktop/services | DevExpress/Crystal Reports generation varies by package | SQL Server; Windows/IIS | Older browser/server dependencies; validate TLS, runtime, reporting, and OS compatibility before change |
| VisualBase 7 | .NET Framework 2.0–4.6.1 components; portal on .NET Framework 4.6.2 | DevExpress 16.2 generation; Crystal Reports | SQL Server; Windows desktop, IIS portal, web/mobile features | Older runtime and browser constraints; use a controlled upgrade path; not suitable for modern cross-platform hosting |
| VisualBase 4–6 | Earlier Windows/.NET Framework generations | Earlier DevExpress/Crystal Reports and portal components | SQL Server and Windows services | End of Support; upgrade required |
Runtime lifecycle conditions
| Product line | Runtime condition |
|---|---|
| VisualBase 12 | Microsoft support for .NET 10 ends 14 Nov 2028. Visualsoft will require an in-version uplift to a then-supported long-term runtime before that date, while keeping the VisualBase 12 support period. |
| VisualBase 11 (Beta) | Microsoft support for .NET 8 ends 10 Nov 2026. The beta line is superseded by VisualBase 12 and will not become a separate general-availability product. |
| VisualBase 10 | .NET Framework 4.8.1 support follows the lifecycle of the underlying Windows operating system. Only Visualsoft-certified, Microsoft-supported Windows versions qualify. |
| VisualBase 8–9 | Microsoft support for .NET Framework 4.6.2 ends 12 Jan 2027. Continued Visualsoft support requires a certified supported-runtime uplift; the original 4.6.2 environment is not supported after that date. |
Product support dates do not extend vendor support for an operating system, runtime, database, browser, reporting engine, or other third-party dependency.
VisualBase 12 verification status
Verification completed so far:
- all 21 platform services build and package successfully;
- all 20 .NET services passed start-up and runtime smoke tests; the Crystal Reports component is unchanged on .NET Framework;
- sign-in, shared sign-in cookies, the security API, tokens and profile, database-backed APIs, Blazor connection, and sign-out were tested.
Not yet verified:
- every screen and workflow action;
- report, dashboard and Crystal Reports rendering;
- the final gateway and load-balancer topology.
These limitations remain listed until the corresponding acceptance testing is complete.