I have downloaded and installed LuaVIEW toolkit v2.0-beta6, and it is working as expected in a development environment (32-bit LabVIEW 2009, 2011 & 2013; on 64-bit Windows 7). We have NOT been successful at getting it to function inside a built executable however. There is an error 13 ("file is not a resource file") when using LV2009, but under LV2013 LuaVIEW tasks just silently fail to execute. We have had success at running LuaVIEW v1.2 inside executables built with both LabVIEW 8.5 and 2009; but have had zero success with built executables using LuaVIEW v2.0 (any beta release) paired with any version of LabVIEW (although we have only tried 2009, 2011 and 2013, all 32-bit). Can you explain any known reasons why this is being so troublesome, or advise us on what to try next?
On a non-technical issue, like Mike Sachs I too wish to know what will be the licensing terms after the eventual release of version 2.0. I need to understand if our existing license(s) will require a fee to upgrade -- plus, assuming this leaves beta and is a released product sometime soon, we will also be requiring more licenses for additional projects.