Release Notes — WUIC Framework v1.7.11
Date: 20 September 2026 Previously published version: 1.7.10 (19 September 2026) Backend: .NET 10 + IIS / Linux nginx Frontend: Angular 21
This version closes two defects that 1.7.10 declared fixed and which kept happening anyway: scaffolded reports printing an empty page, and scaffolding a table from the interface answering with an error. They were found by the same round of installs on clean machines that produced the previous version, repeated this time against the published product to check the fixes. They still affect those who do not use SQL Server.
📊 Scaffolded reports really print their data on MySQL and PostgreSQL
1.7.10 introduced the rewriting of the query of reports generated by the framework, because the .mrt that ships inside the package carries the identifiers of the engine it was created on. That rewriting never ran, though: it looked the metadata table up by the name of the dictionary database — which is always Connessione — instead of the name of the data source, which is the route. Finding no table by that name, it returned silently, rewrote nothing and left no trace, and the report kept printing the page with its header and not a single row.
The route is now read from the right place, and every case where the rewriting cannot happen — no table by that name, table with no columns — leaves a line in the backend log. An empty report with no explanation is exactly what made this defect hard to see.
If you have generated reports that printed blank on MySQL or PostgreSQL, there is nothing to regenerate: just open them again.
🧱 Scaffolding a table from the interface on Oracle
On Oracle, generating a table from the interface answered HTTP 500 with ORA-00001: unique constraint ... violated on the menu table, and the route was never created.
It is the same defect fixed for PostgreSQL in the previous version, left uncovered on Oracle. The schema declares the menu key as GENERATED BY DEFAULT AS IDENTITY, but the framework inserts its own system entries with the key computed by hand: the generator does not advance, and the first row that relies on it asks for a key that is already taken. Realigning the generator now covers both engines.
📦 Updated packages
| Package | From | To |
|---|---|---|
WuicCore |
1.7.10 | 1.7.11 |
Wuic.Webcore |
1.7.10 | 1.7.11 |
WuicOData |
1.7.10 | 1.7.11 |
RuntimeEfCore |
1.7.10 | 1.7.11 |
Wuic.MySqlProvider |
1.7.10 | 1.7.11 |
Wuic.PostgresProvider |
1.7.10 | 1.7.11 |
Wuic.OracleProvider |
1.7.10 | 1.7.11 |
wuic-framework-lib (npm) |
1.7.10 | 1.7.11 |
🔧 Recommended operational updates
- No configuration change: the
appsettings.jsonkeys are unchanged. - If you have generated reports on MySQL or PostgreSQL that printed blank, open them again: the query is rewritten at render time, there is nothing to regenerate.
- On Oracle, if scaffolding a table from the interface answered with a duplicate key error, try again: the menu key generator is realigned after every insert with an explicit key.