Breaking changes
(Created page with "==== MDriven Framework : we now require legal ocl in all oclColumns ==== Starting from 2018 and the support for VS2019 we made changes related to efficient load that make the...")
 
Line 11: Line 11:
  /// </summary>
  /// </summary>
  AbstractDeriver.ThrowExceptionOnFailedDerivation=false
  AbstractDeriver.ThrowExceptionOnFailedDerivation=false
==== MDriven Framework : VariableHandle changed default on AddDefaultNestings and  AddDefaultProperties from true to false ====
Earlier we had AddDefaultNestings and AddDefaultProperties=true as default and this was introducing extra load that was not necessarily asked for. If you want to use "self" a better option is to set AddSelfColumn on the variableHandle

Revision as of 18:55, 8 November 2020

MDriven Framework : we now require legal ocl in all oclColumns

Starting from 2018 and the support for VS2019 we made changes related to efficient load that make the framework check all oclColumns.

Prior to this point oclColumns could be ignored if no-one ever used them - but now - we assume that they are all used and thus valid. This is inline with our shift from placed handles to compound declarative ViewModels that are statically checked along with the model.

We will now throw exception if a n illegal ocl is found in the derivation phase.

If you would rather just log this with trace you can do so by setting the new variable:

/// <summary>
/// Set this property to false (default true) if you only want trace logging of failing derivations
/// </summary>
AbstractDeriver.ThrowExceptionOnFailedDerivation=false

MDriven Framework : VariableHandle changed default on AddDefaultNestings and AddDefaultProperties from true to false

Earlier we had AddDefaultNestings and AddDefaultProperties=true as default and this was introducing extra load that was not necessarily asked for. If you want to use "self" a better option is to set AddSelfColumn on the variableHandle

This page was edited 99 days ago on 02/10/2024. What links here