The Verum team is pleased to announce that starting with the 31st of March 2017 Dezyne Release 2.3.0 is available for download.

On the 10th of April 2017 dzn service version 2.3.1 replaced service version 2.3.0 as Default with a change in the handling of thread-shell in C#.

On the 13th of April 2017 Dezyne (Eclipse plugin) 2.3.1 replaced version 2.3.0 with a change in the version of the Node.js (with npm) which is installed on the user’s system and with a fix for use of the Built-in browser, and dzn service version 2.3.2 replaced service version 2.3.1 as Default with a fix for verification/simulation of interface models specified in a namespace.

On the 9th of May 2017 dzn service version 2.3.3 replaced service version 2.3.2 as Default with a fix for handling out parameters in combination with 'blocking' in C#.

On the 7th of June 2017 dzn service version 2.3.4 replaced service version 2.3.3 as Default with fixes in the C# runtime, for example a fix for an out of range exception.

This version is free for non-commercial use.

If you are interested in a license for commercial evaluation or commercial usage, please contact

New features and improvements

Version 2.3.x is an extension of Release 2.2.0. The main theme of the release is ‘Improved user experience and extended C# support ’. This is an indicative list of new features and improvements:

  • Support for blocking in C#

  • Improved error messages including improved explanations

  • Improved auto completion during model editing

  • Improved communication between the System View and the Model Editor

  • Improvements related to installation of Dezyne

Due to changes in the Dezyne runtime you have to replace the old Dezyne runtime in your projects with the new one.

Solved issues

  • 7300 Eclipse error: Could not create browser (solved by Dezyne (Eclipse plugin) 2.3.1)

  • 7299 Unclear Verification Error (solved by dzn service version 2.3.2)

  • 7292 code generation not working when file without extension is present

  • 7284 Two copies of Dezyne show the same simulation trace

  • 7283 High Client CPU loading on long verifications

  • 7282 Implement click and Ctrl+click for ports in the system view

  • 7281 System View inconsistency

  • 7255 Confusing feedback after finding an error during verification

  • 7253 Auto-complete suggestion

  • 7228 Not all menu actions will be executed on all selected files

  • 7208 Incomplete generated code (C++, C++-msvc11) when blocking an event in combination with an out parameter

  • 7173 The Simulator is confused and displays misleading lifeline when component name is the same as the name of the provided interface instance

  • 7164 simulator gives deadlock while verifier finds no errors

  • 7160 Refactor conversion of multi threaded ASD model

  • 7157 After conversion from ASD there is a slow verification without an obvious reason

  • 7156 Cannot convert from ASD:Suite model

  • 7150 Generate foreign components (for system view), during model conversion, also for models where the reference name of a foreign component differs from the interface of that foreign component

  • 7109 Target language support for C#

  • 7030 Interactive error message hides line it applies to

  • 6963 Simulator does not report range error

  • 6949 Allow creation of new project (new folder) on File --> Save As

  • 6851 Code completion not working for enum state variable in a guard statement like [state. …​]

Important message for Dezyne users on Windows

  • Due to file locking policies and permission issues users who are using Dezyne on a Windows system are required to remove their Node.js (with npm) installation (self installed or previously installed by Dezyne) and stop all ‘node.exe’ processes (via the Task Manager) before running the Dezyne Eclipse GUI 2.3.x for the first time.

    • if self installed: remove the 'npm' and 'npm-cache' directories from 'C:\Users\windowsusername\AppData\Roaming' and uninstall 'Node.js' via the 'Control Panel'

    • if installed by Dezyne: remove the 'node-v6.2.1-win-x64' directory from 'C:\Users\windowsusername'

on first start-up of Dezyne the latest stable version of Node.js (with npm) will be installed on your system. Additionally, the Dezyne command line client (together with a daemon) will also be installed.

Known issues

  • Views (i.e. system views, state charts, state and event tables) are not cleared if they can not be updated due to an error in the model or due to missing data

For a complete list of known issues click on the followinglink: Known issues in Dezyne

Your free copy of Dezyne is waiting for you, and we encourage you to put Dezyne 2.3.x to good use and provide us with all your feedback.

Good Dezyning!

The Verum team.