This section outlines new features in the EPC140006 version of VLF-WEB and VLF.NET.
| VLF.NET no longer supports using aXes-TS as the RAMP execution engine The use of aXes-TS as the execution engine for RAMP in VLF.NET applications is no longer officially supported. VLF.NET applications that use aXes-TS as their RAMP engine will need to be changed to us the aXes-TS2 engine. |
| XUA compatibility and document mode changes in VLF-WEB and VLF.NET As part of the move towards using standards compliant web browsers, all VLF-WEB and VLF.NET contexts now use: <!DOCTYPE html> The single exception is when VLF-WEB start-up pages are generated on a developer PC that that has a “Deployment Server” defined to use the aXes-TS execution engine. In that context these tags are used: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN" "http://www.w3.org/TR/html4/frameset.dtd"> Note: These changes may impact existing applications so you should test this VLF version in a development environment before deploying to production systems. |