JavaScript must be enabled in order to use this site. Please enable JavaScript in your browser and refresh the page. Migrating VDL 2.0 Apps to VDL 4.x There are several steps to take when converting a VDL 2.0 app to VDL 4.x. Change the VDL version of your VDL file. Namespacing tags and attributes. AutoText changes. Convert customer runner code to script blocks. Table modifiers. Remove custom runner references from the companion file. Remove handlebars references, replacing with VDL 4.x equivalents. Covered Topics Change the Version of your VDL File You need to change the root tag of your VDL file. Namespacing Tags and Attributes In VDL 3 the decision was made to namespace all non HTML5 tags. AutoText Changes Where VDL 2.0 had the autotext and text tags, VDL 4.7 has the single attribute vdl-text. Converting Custom Runner Code to Script Blocks In VDL 2.0 the custom runner file allowed the view developer to layer on extra scripted functionality. Table Modifiers One of the main uses for a custom runner was to add functionality to AutoTables. Removing Custom Runner References from the Companion File Remove any references to custom runners in the companion file. Removing Handlebars References In VDL 2.0 dynamic access to some entities, scenario properties and loop variables was achieved with the so-called Handlebars syntax. Parent Topic Upgrade Guide