Search the Community

So, here is the problem: I want to access the build version of my EXE with a post build action VI. My goal is to modify the welcome message in the installer build spec to include the build version. If that fails, I want to at least generate a file that can be included with the installer to label the build version. Ideally, I would like to place the build in a folder that incorporates the version in the name. Not sure yet how to accomplish this in an automated way, but the first thing to tackle is getting the version of the EXE. I have come up with three ways to do this: 1. use project properties to extract this information (so far, a major PITA) 2. extract the information from the project file using XML tools. (also a PITA, just in a different way) 3. after the EXE is generated, use .net calls to read out the version information. My question is, has anyone already solved this? Do you have a stable and elegant solution you can share? If not, do you have any other suggestions on how to do this? For the NI guys, why is this so hard? Shouldn't this info be easy to access? Why should it be hard to make an installer that tells the use what version they are about to install? Does anyone else have their own custom build system that does automated builds to new folders every night/week/etc? How do you do it? thanks for any help or ideas. -John

Hallo everybody, I have created a new add-on for LabVIEW called "TTM" that helps me a lot to automate some boring activities as: save source code into a zip file with build version, to keep my projects syncronized with executables, send emails to my test group or my customers with attachements, transfer my builds to my web site, using ftp protocol manage files and folders zip/unzip source code files execute custom VIs into my script inject license codes into my executables before creating installers (if you use instant plus, TTM's great for you) other tedious stuff it is programmable, it's easy and other developers save a lot of time with it. I think can be usefull to you also. It can be downloaded at http://www.toolsfors...roducts/TTM.php Claudio Vivante ... ops... I forget to write that TTM works with LabVIEW 2010 and LabvIEW 2011 only. sorry Claudio