Release Date: March 30, 2026
Important Note: We strongly recommend testing this update in a non-production (test) environment before deploying to production.
What’s New & Improved
.NET 10 Migration
VDM has been upgraded from .NET Framework 4.8.1 to .NET 10. This transition required significant refactoring across nearly the entire VDM platform.
As part of this upgrade, the following runtimes are now required:
aspnetcore-runtime-10.0.5-win-x64.exe
windowsdesktop-runtime-10.0.5-win-x64.exe
Additionally, MicrosoftEdgeWebView2RuntimeInstallerX64.exe may be required on systems where it is not already installed. Most Windows 10, Windows 11, Server 2022, and Server 2025 environments include this runtime by default; however, some Server 2019 environments may require a manual installation.
Going forward, our goal is to remain aligned with the current .NET Long-Term Support (LTS) releases to ensure continued performance, security, and compatibility improvements.
Bridgit Analysis
We are introducing a new Bridgit Chat UI along with a new feature: Bridgit Analysis.
Bridgit Analysis enables automated analysis of Finished Reports and Visualizations using OpenAI’s API. The system leverages advanced language models (currently GPT-5.4) to generate structured, written insights based on report data.
Key capabilities include:
- On-demand analysis of Finished Reports and Visualizations
- Interactive chat with your Finished Reports and Visualizations
- Configurable tool usage, system prompts, and user prompts at the report level
- Automated analysis via Scheduler with email delivery of generated insights
This feature has been tested across a wide range of report types and is designed to provide consistent, readable summaries and interpretations of report data.
Finished Report Serialization Updates
As part of the migration to .NET 10, support for CodeDom has been removed. Any Finished Reports that rely on CodeDom (typically reports created in v12 or earlier) must be updated to the newer serialization format to be compatible with WebReports.
To support this transition:
- Finished Reports are automatically detected and upgraded when opened in VDM
- A Batch Upgrade FR tool is available under the Help menu to upgrade reports in bulk
The batch upgrade utility allows users to update all applicable reports without needing to manually open, modify, and save each report individually.
DPI Awareness
VDM is now DPI-aware, improving how the application scales across different screen resolutions and display scaling settings. This ensures a clearer and more consistent visual experience based on each user’s display configuration.
If any display or scaling issues are encountered, users can enable High DPI Scaling Override on the application shortcut:
- Right-click the VDM shortcut and select Properties
- Navigate to the Compatibility tab
- Select Change high DPI settings
- Enable Override high DPI scaling behavior and set it to System
Scheduler SQL Connection Options
As part of the .NET 10 migration, SQL-based scheduler connections have been updated to support current connection requirements.
Older scheduler SQL connections may not have required the Encrypt Connection and Trust Server Certificate settings. Under .NET 10, these options may now be necessary in some environments for successful SQL connectivity.
To support this change, scheduler profiles now include these connection settings so they can be configured as needed for compatibility.
Bug Fixes
Parameter - Enabled By Query Blank Parameter Page Handling (Bug 1748)
A parameter page could still display as a blank page when all parameters on that page were hidden by Enabled By Query logic. This occurred because a flag was being set even when parameters were not displayed, causing the page to appear instead of being skipped. Testing confirmed that pages with no visible parameters are now skipped correctly, and that the page still appears as expected when the query condition allows the parameter to be shown.
Parameters - Enabled By Query Default Value Handling (Bug 1750)
A dynamic query used by an Enabled By Query condition could fail when it depended on another parameter that had not been manually set by the user. In that situation, the query only evaluated the parameter’s current value and did not fall back to its default value, which could cause the conditional behavior to work incorrectly. This was corrected by adding a check to use the parameter’s default value when no explicit value has been set. Validation confirmed the issue was resolved.
Parameter - First Disabled Parameter Preventing Prompt Display (Bug 1791)
A parameter prompt page could fail to display when the first parameter on the page was disabled, even if additional parameters on that page were still enabled. This made the page appear as though no parameters were available. The issue was corrected so that the prompt page now renders properly whenever any parameters on the page remain enabled. Testing confirmed that when the first parameter is disabled and subsequent parameters are enabled, only the enabled parameters are shown as expected.
Comments
0 comments
Please sign in to leave a comment.