Number of Build EXE programmatically

I've seen discussions to find the Build number of the EXE using calls .NET or dll.  One of the latest versions of LabVIEW have this property built in (so that I could call him in my application)?  Looks like such a common need, do not know why it was not included (or else I can't find it, I looked everywhere for it...).  Thanks for the help in advance.

There is something built-in, although it uses a call to the DLL - vi.lib\platform\fileVersionInfo.llb

As far as I know, which should retrieve the version number, you define in the build.

Tags: NI Software

Similar Questions

  • Display number in build request.

    I found a few old threads about it with no solution, but nothing recent. Does anyone know if there is a simple method to display the version number of an executable built with the manufacturer of the application. I have the build to set to auto increment and would like to be able to see this number in the installed application.

    For the love of light, I mean the build number of the exe file, not the version number of the installer again that I create.

    At present, it seems I have to manually assign a version number and construction and make it visible in the application. For this, I use a different 'about' available from the main routine vi.

    All suggestions welcome.

    I'm using LabVIEW 8.6.1 on Win XP

    Best regards

    Bandit.

    Bandit wrote:

    @ smercurio_fc - which sounds very promising. We are far outside my zone of comfort here...

    Assume I know nothing on .NET, you won't be far from the truth.

    What class do you need select invoke, in the node to access the FileVersionInfo method?

    And it requires specific .NET already installed on the computer, things that maybe I don't have no control is the target?

    There is an example here: http://digital.ni.com/public.nsf/allkb/D45E3A1E694815AD86257173005CFD36

    You will need to have installed .NET, and this solution is specific to Windows.

  • Export data to Excel does not work in the build (.exe)

    I'm new to LabView 2010, but made a small application which works as expected when run as a VI in the Labview environment. This is a simple data acquisition where the results are displayed in a waveform graph. I used the method "Export data to Excel" to present the request to transfer the results on the chart in an Excel file programmatically.

    However, when I build the application and run the exe, the application works very well outside the export to Excel. Excel does not start, and when I right click on the graph for "export data to Excel" manually, it doesn't work anymore. The data can be exported to the Clipboard and then pasted into Excel, which is doable, but not very elegant solution...

    Any thoughts?

    Hi CFNoergaard,

    This issue has been corrected in LabVIEW 2010 SP1.

    If you upgrade to this version, it should do the trick.

  • Building exe problem

    When you try to build an .exe, I got the following error...

    Error 6a held at AB_Source_VI.lvclass:Close_Reference.vi-> AB_Build.lvclass:Copy_Files.vi-> AB_Application.lvclass:Copy_Files.vi-> AB_EXE.lvclass:Copy_Files.vi-> AB_Build.lvclass:Build.vi-> AB_Application.lvclass:Build.vi-> AB_EXE.lvclass:Build.vi-> AB_Engine_Build.vi-> AB_Build_Invoke.vi-> AB_Build_Invoke.vi.ProxyCaller

    Possible reasons:

    LabVIEW: File generic i/o error.
    =========================
    NOR-488: IO abandoned operation.

    Have no idea why... the vi works perfectly, but cannot generate the .exe.

    Help, please.

    I used the LabVIEW 8.x. (build Advanced Menu) file structure

    Problem sovled.

  • Writing PNG file failed when build exe, but operate normally on the development platform

    See photo below, it is used to call WinAPI for screenshot and then save it in PNG file. This Vi operate normally on the flatform of development, but it failed when building the application .exe file. The pop-up dialog error 'chain of illegal path, OS', but it is clear that the path is correct. Note: run the same PC with Win XP.

    Update:

    I found the reason, but not a solution. In fact, the Clipboard.Get Image does not work when building application exe. But it's the private node invoke, impossible to get support of NOR.

    It seems to be to the node to invoke public on the version of LabVIEW 2012, which can help you check on LV2012 version? Thank you very much.

  • How To Build exe for previous Versions

    I am a bit new to LabView and still struggilng with all the files associated with a project, so I don't know that it is a simple question.

    I'm under LabView v10 for development, but wants to create an exe that run on a version of the runtime v8.5. I've seen threads that suggests it's as simple as 'Save for the previous Version'... but for some reason I can't seem to make this work. I tried to save the vi for 8.5, then by choosing to build the exe, but to be invited to create a project, I thought it has not saved changes - that the Subvi have been converted to version 10. I tried to reduce the changes and opting to use those memory, but it does not; exe built then gives me a runtime error, complaining that isn't time LV 10.

    I tried to save the project with 'Save for the previous Version', and then construction. Yet once, it works not even if when I opened, and then immediately close or the project, or it contained VI, I thought it has not saved changes where it was converted in LV10 - implying the indeed saved files in LV8.5 format.

    I seem to go along in circles here. What is mind someone on the steps needed to build an exe that run on a previous runtime environment?

    Thanks in advance

    To my knowledge, none of the device drivers of OR may have multiple versions co-exist.  Now, who does not necessarily mean if you use any material that you will encounter problems.  If the material is material OR, then they will also have specific drivers that may be conflicting, but if they are from another manufacturer, it will come down to NI-VISA probably.  If you use data acquisition cards, then you have installed DAQmx.

    As long as your program is not access to these devices, you're OK.  Do not update the drivers if you do not use the equipment.  You need to look for in the relase notes each of the drivers you need to update and see if you can find a version that supports 8.5 and LV2010.

    Even if you do this, it is not 100% guaranteed that you will have problems.  I wrote an application for a client once used OR-DAMA.  I had a control on the front panel, based on a typedef in the pilot.  I've updated my laptop for a new project, but later had to come back and do an update for the original project.  The typedef had changed and caused a recompilation.  Nothing broken on my end.  When I sent the update, it crashed on the PC of the client due to the change of the typedef.  I ended up bringing to upgrade the driver on their machine.

  • Build exe error involvving internal.llb

    Hi all

    I have built many exe, but for some reason, this one is hard!  I get an error that says:

    Error 1003 has occurred at \\Rochester\mtp\Test Rigs\NC4\NC4 Air Cap\Code Development\Air CAP v2.0\exe\internal.llb\Air v2.1.vi Rig inspection Cap

    I spent reviewing the many forum posts that suggest that one of sub vi is not executable.  The main and all vi the subvi will be running in the labview environment.  I tried a forced compilation and even a massive compilation.  All to nothing does not.  This problem occurs on two different PC and build other similar thin vi, so I guess it isn't a problem with the manufacturer.

    I'm using LabVIEW 7.1, 8.0 Vision and IMAQ 3.5.1: see attached report for good measure.

    Can you help me?

    If you need to sub that VI let me know.

    Dan

    Hi Jordan,.

    I couldn't see anything wrong with the individual sub - vi and I tried your suggestions.  Turns out in the end a problem with the opening of the workbook with a password.  There is no security on the daughter to excel, but the vi has been programmed to use a.  If I removed the password of the vi it does not open so I added a password for the excel file and - hey presto! -everything works and relies on an exe file!

    I have not tried on the machine yet, but I am optimisic that it will work.

    I think it's for lack of microsofts!

    Thanks for your suggestions; you reduced to the excel link.

    See you soon,.

    Dan

  • the application builder exe file does not work

    Hi all

    I have a usb data acquisition module, it is USB 2408-2AO of MC. I order the module with a VI and it works very well. I used the Application Builder to create an exe of the VI. The exe works great too, but only on my own computer and not on other computers.

    I already made the other screws's exe files and never had any problems to run the exe on other machines. I also tried to do an installation of the VI program and not just a stand-alone application, but once again the final application does not work. The application runs without problem on the target computer, no errors are displayed, but it just does not control the USB module as it should. I think the problem is that the builder Application does not include al screws required in the installation program, particularly MC devices to control the USB device. I tried to manually choose the screws, but it seems that everything is included... I am sure that the problem is the USB device, as I did other exe files and they all work very well (but they do not control the USB device) on other machines. Someone has any idea how to solve the problem?


  • 2009 build exe error

    I f3 2009 installed on an XP sp3 machine and I am trying to build an executable and get the error below.  I can find the error.llb and the vi in question.  I opened it even without any problem.

    I've included the vi I'm turning into an exe file, thought that it might help.  The name of the exe is supposed to be "hydrogen diagnostic distribution".

    Any ideas on how to solve this problem?

    An error occurred during the recording of the following file:

    C:\Program NIUninstaller Instruments\LabVIEW 2009\vi.lib\Utility\error.llb\GetRTHostConnectedProp.vi

    Invoke the node in AB_Source_VI.lvclass:Close_Reference.vi-> AB_Build.lvclass:Copy_Files.vi-> AB_Application.lvclass:Copy_Files.vi-> AB_EXE.lvclass:Copy_Files.vi-> AB_Build.lvclass:Build.vi-> AB_Application.lvclass:Build.vi-> AB_EXE.lvclass:Build.vi-> AB_Build.lvclass:Build_from_Wizard.vi-> AB_UI_Frmwk_Build.lvclass:Build.vi-> AB_UI_FRAMEWORK.vi-> AB_CreateNewWizard_Invoke_CORE.vi-> EBUIP_CreateNewWizard_Invoke.vi-> EBUIP_CreateNewWizard_Invoke.vi.ProxyCaller

    Method name: Save target: Instrument

    Strange.  I did some research more around and tried to check the 'use LabVIEW 8.x file layout' in advanced generation options and it doesn't have a problem.

    I have no idea why this worked, but it did.

  • Panel before change afte build EXE

    HI guys,.

    I'm building a program with a custom control on the façade, but the façade was changed after an EXE and the custom control have become very big and blurry.  I'm trying to build it on another conputer, the façade will also be Cissé after an EXE.

    any help will be appreciated.

    I was recently working with images on the Boolean buttons and came across this video.  http://forums.jkisoft.com/index.php?showtopic=490  I recommend you watch.  Even if you do not need to do exactly what they're doing, it gives a pretty good overview of various features of the control editor.

    I think that you are dealing with a few problems.

    1. you have pasted a picture in the Boolean text in the control.  It causes the image resizing.  I came across this in a weird way when I was working on a button with an image pasted into a text Boolean and things happening on my Vista system, but looked distorted when I took the VI for an XP system.  (A caused different system font size different to the police, even if the font size was the same, and the embedded image changed accordingly.)  When I had this problem, the research forums led me to a message thread that linked to this video and who showed me how I was doing bad things.

    2. your screenshot shows that you do business with a Chinese or Japanese or some other set of Oriental characters.  All these crazy characters seem to not be working on computers and have weird characters sets that make all sorts of unpredictable things.

    Watch this video.  Learn more about the parts window in the editor control.  Watch collage photo stickers, or with the way that they customize the controls.  Don't mess with paste images into the text field of the control parft.  Start over from scratch, customization of the Boolean buttons to achieve the desired appearance according to what you learn from this video.

  • Build EXE Error _ BeginUpdateResourceA.vi

    Have you guys ever seen this error before?

    "Generation failed...". Error 1 has occurred in BeginUpdateResourceA.vi.

    I looked for the file named "BeginUpdateResourceA.vi", but I couldn't find it. The file is not in the project of course.  The error only occurs to my customer's system.

    Configurations:

    1 LabVIEW Professional Development System 2013 SP1

    2. the source VI is a TestStand Custom operator Interface. Other normal screws are good build.

    3. There is no problem before installing a security program that is provided by my client ' coporate. The program periodically checks each file in the system.

    If you have the solution to this problem, please let me know.

    Best regards

    Joonam

    Let me add that I have seen this error before and what it it make me feel again this morning.  It worked fine until my last code (minor) update.  On a whim, I just to build another executable in the same project (which worked well) and when to try again with the first specification to build, had "error 1 has occurred in EndUpdateResourceA.vi"

    This thread has some changes to begin... vi.  Mr._Jim suggested:

    1. Mass of the entire application of the compilation directory

    2. LabVIEW of closure and reopening

    I would like a solution to this.  Maybe it'll go away when I switch to LV2014?  Maybe I'll just blame my lousy computer and go home...

  • Get the serial number, otherwise building

    Hello... I hope someone here can help me with a bit of a conundrum...

    I bought a computer recently used, a transaction that included the purchase of a copy of CS5 Design Premium on said computer. Be distracted at a time and only interested in getting the House thing, I forgot to ask the serial number of the product to the seller at the time (and I don't have the disc) and I have now hard to get back in touch with him.

    Is not the original purchaser, I run into stumbling blocks in trying to figure out the serial number of the software. What can I do here in case I can't make contact with him again? I would like to move the software to a new computer, but cannot do so if I'm not able to activate it, and all the Adobe support forums to assume that I can just check my e-mail/disc box.

    I'm sorry but not really because there was no transfer of property and you have more serial number available.

  • How to obtain the build version of the exe when running

    Hi all!

    Is there a way to get the build number of the EXE file in the runtime?

    There are version field in the exe, property that can be autoincremented construction each construction process.

    It will be very useful to show in a particular area on the application window.

    But I can see now that in the operatin system file property.

    I couldn't find this point between the nodes of the Application property.

    Perhaps this information available in rintime by another way?

    I now use LV2010 on Windows XP/Win7 platforms.

    Thanks in advance for any ideas.

    Anatoly

    Hello

    Have a look here.

    http://forums.NI.com/T5/LabVIEW/file-version-info/m-p/361945?jump=true

    Tyler

  • build the EXE function not found

    Hello

    I'm working on Labview 8.0... The problem I am facing is, I can't find the option to build EXE in tools... I installed all the packages properly... and I also tried to reinstall all lv... but always the option of compiling exe is missing... Can someone tell me how to find it?

    Kind regards

    Nitzy

    Are you sure you have the professional edition on both machines? The Application Builder is included in this edition. For the Base or Full, you will need to buy it separately.

    As I have noted, from LabVIEW 8 you must use projects to create applications. This is explained in the help of LabVIEW, and describes the steps for creating an application. This article also contains the steps: Distribute the Applications LabVIEW Application Builder.

  • Error 1502: help... can't build my exe

    Hello

    I am stuck and tried all advice warmly 1502 error in order to build an exe from the "RS_Init_SSH2.vi" file in the attached zip.

    I use LabVIEW 2012 and never experience while building exe until I have add this prtoblems vi.

    Note that enabling of mode in the debug compiler makes build ok but the exe resulted in lack of other dependencies and actually leads to more problems on my side.

    I hope that this issue is just one small thing that someone could help me find the cause of this problem.

    Thanks in advance for your support,

    BR,

    BIM

    I'm using LabVIEW 2013 and I have no problem to create an executable file. However, there is still a missing file (command: Cl_ssh_connect.ctl).

    I went down again while LabVIEW 2012 and you can check.

Maybe you are looking for

  • MacBook Air keyboard does not properly

    My MacBook Air keyboard types the front slash after I typed the letters L, O and the period. Then he begins typing the non-stop before slash.  I can stop it for a second when I type a different letter, but it again immediately.  I pressed on the ' |

  • gives USB mass storage driver '!' mark

    After working continuously for a long time my system becomes unable to recognize the USB. This mass storage driver USB of time in the driver manager gives '!' sign. The problem disappears once I restart the computer. My laptop model is Pavilion g6 &

  • a problem with an installation of memory

    Hello I have trouble to install memory in addition to my currnt one card. When I use the old one only it workes very well. When I use both my cmputer won't turn on. Instead, I hear 5 sound "beep". It lights when I use my new single memory as well. I

  • Do my 8610 the default printer

    I have installed and uninstalled my new printer at least 3 times.  When installing, I had a default error message could not be set.  Now when I go into Control Panel, it will not put a check mark next to the printer to make it the default.  I did not

  • The calendar appt private value

    I created a new appt in the calendar. Is there a method put in private?  I don't see a flag in the doc. THX