Jump to content

Search the Community

Showing results for tags 'build'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Software & Hardware Discussions
    • LabVIEW Community Edition
    • LabVIEW General
    • LabVIEW (By Category)
    • Hardware
  • Resources
    • LabVIEW Getting Started
    • GCentral
    • Code Repository (Certified)
    • LAVA Code on LabVIEW Tools Network
    • Code In-Development
    • OpenG
  • Community
    • LAVA Lounge
    • LabVIEW Feedback for NI
    • LabVIEW Ecosystem
  • LAVA Site Related
    • Site Feedback & Support
    • Wiki Help

Categories

  • *Uncertified*
  • LabVIEW Tools Network Certified
  • LabVIEW API
    • VI Scripting
    • JKI Right-Click Framework Plugins
    • Quick Drop Plugins
    • XNodes
  • General
  • User Interface
    • X-Controls
  • LabVIEW IDE
    • Custom Probes
  • LabVIEW OOP
  • Database & File IO
  • Machine Vision & Imaging
  • Remote Control, Monitoring and the Internet
  • Hardware

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Personal Website


Company Website


Twitter Name


LinkedIn Profile


Facebook Page


Location


Interests

Found 10 results

  1. This is a DSC module question: has anybody here experience with building standalone executables which include shared variables bound to DSC modbus i/o servers? I have an issue with deployment, possibly related to licensing. I posted on the dark side, but haven't got feedback yet. https://forums.ni.com/t5/LabVIEW/shared-variable-bound-to-Modbus-i-o-not-working-in-deployed/td-p/3809801 TIA, Enrico
  2. Overview In order to quickly and efficiently prepare source for distribution, a build system was necessary to abstract away the conversion of source into the different types of deliverables (VIPackages, Executables, dlls, ect) as well as abstract away the build order of our software hierarchy. Many have undertaken to solve this problem. I don't claim to have created a silver bullet. But I do hope that the system I've put together (and am releasing as open source) will act as a starting point for you to extend and customize to meet your needs. I've endeavored to employ good softw
  3. Hi Everyone, Most of the time I am able to find solutions to my issues just by reading this forum but I wasn't that lucky this time. So, i got an issue when i'm trying to install my build. I got the following message: "This distribution is built with an older version of winMIF that is not compatible with .NET 4.6.2 upgrade to 17.0" When googling this error message or even "winMIF" i can't find anything that match my request I tried to uninstall the .NET framework and then reinstall the 4.0 (and 3.5) and I got the same issue. (Exactly the same error even if it's .NET 4.0
  4. I need to read the installer version number (not the exe version number) programmatically. Is there any way? I have a bundled software which has multiple EXE's under one installer. Commonly I use the installer version number for reference and want to show it up to the user. Is there any way to get the installer's version number instead of executable's version number? --Ajay.
  5. Hi, I posted this question in OOP forum, but may be the right place is here... Have you experienced that LV takes very long time to build executables when you use a certain number of classes? I have noticed that when my app uses many classes (e.g. 30 classes) LabVIEW IDE slows down ("busy pointer" appears very often during VI editing) and compiling executables takes more than half an hour. It's not due to my machine because larger projects are built in less time if they don't contain so many classes. Are there properties that can speed up the build?
  6. Hello all, I am trying to integrate our LabVIEW build workflow into our CI Server. Currently we have several builds in LabVIEW projects that we can programmatically call in order to perform the build, conduct unit testing etc. using the IDE. I'm looking to integrate this into our build server using TeamCity. Every time we check in changes to one of the projects a build is triggered. Since building requires the IDE running, I am attempting to use the Command-line Runner in TeamCity to execute a batch file that launches the IDE with the builder VI as an argument. The build VI performs th
  7. 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 p
  8. I wrote a very simple vi for a friend of mine. Simple as in: this vi has no sub-vi's and all functions are from the standard palette. I was going to build an executable for him to run it, but it turns out he has a Mac and I am running on Windows. Even though I own 3 licenses of LabVIEW it appears that I have to purchase a whole new multi-thousand dollar LabVIEW license for Mac to be able to build it. Given the nature of the project, you can see why this is not a good solution for the situation. I am asking for a favor, that if anyone has the Mac OS version of LabVIEW if they wouldn'
  9. Hi I have designed an application for my graduation project,now i need to built it but i don't have the key for that !! If any one have the application builder key,and he want to help me i will send him my (.VI) file,he build it and then he send me th (.exe) file I don't know if such demand is possible but i really need ur help !! So please help me thx
  10. Hi folks, I have created an executable with LV 2011 and I have found an unexpected behaviour of my application: the VI's menu uses an unreadable font or charset. When I run the same VI from LabVIEW (i.e. the source code), I see the standard LabVIEW menu. Above you see the screenshot of panel executed from LabVIEW IDE, below you see the same VI executed in my .exe app. browsing submenus I see the strange font in every submenu. Instead, labels and captions on panel have standard font. In past, I have built other applications on the same machine, all worked fine. Have you any idea? are
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.