Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation


About dcoons

  • Rank
    LAVA groupie

LabVIEW Information

  • Version
    LabVIEW 2018
  • Since

Contact Methods

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Looks like this is what I need - here is updated project with some implementation to prove it out. Thanks @Darren Example Project.zip
  2. Here is an example project to entice you more. Template gets copied, library gets renamed, a few edits to the PPL build, and then I need to edit the installer. I am pretty sure I can use the tags like below - but I know that isn't the best way to do this. Example Project.zip
  3. Has anyone used the functions located in vi.lib to programmatically edit Installer build specifications? I have used the functions in AB_API to edit Packed Project Library build specifications (in PPL subfolder) but cannot find anything equivalent for Installers. The classes in this hierarchy inherit from NI_AB_API_Build.lvclass which has a generic open method, but installer is not in the list of selectable build types to open. I also found IB_Classes subfolder which has functions for interacting with Installers maybe, but there's no clear function to open an Installer build specification to start editing. I have a template project where I need to change three parameters for the Installer when the template is copied/edited: destination.name for one specific destination, INST_bldLocation, and INST_productName. This is an example of updating a few of the build specification items for a PPL (just need the equivalent for installers):
  4. As an update, here is an example code project demonstrating to a minimal degree what I am trying to accomplish. In this case the VIPM package will go to user.lib, but the same issue still applies. (Also, I made a .vip file, but you can just take the built packed library and put it into user.lib instead of using the package and it will still demonstrate the issues) -Common Code has a reuse function I want to use and it is built into a packed library -Parent defines a parent class that uses a function from common code and is built into a packed library -Child class inherits from Parent but Parent is Not Loaded and breaks Child class vi.lib reuse issue.zip
  5. The Limits.lvlibp stays Not Loaded even when Controls.lvlibp is added to the project. It doesn't make anything worse, just doesn't change anything.
  6. Inspired by my question from this post: link, I started off on a path of packaging project dependencies into vi.lib as suggested by @smithd and @Darren however I have started down a rabbit hole of packed project library (ppl, *.lvlibp) head scratchers that have left me a little confused on what is going on in the background. Most of my components are built into packed libraries because I am following plugin models for extensibility when building as an EXE. To make packed libraries work with dependencies, you basically have to build those into packed libraries as well to avoid the namespace issues. I used VIPM to create packages to distribute some of this shared code to vi.lib. In the example below, I created a packed library (Controls.lvlibp) and packaged it to vi.lib for use. In the Limits project in the image, I am using the Controls library in a few of the functions. Limits also contains a build specification to create a packed library for a component. However, I first noticed an issue when I looked at my child class projects (that inherit from the Limits.lvlibp:Limits.lvclass). The Limits.lvlibp is showing as Not Loaded. When I go directly to the library on disk and try to open it, I get the message "Project or Library file cannot be opened." I notice that if I get the correct Controls.lvlibp into memory by opening it up or by putting one of its VIs on a block diagram, then the library will load correctly. So, I know it has something to do with when data from vi.lib is loaded into memory, but I don't know how to force it into memory to get this to work correctly. Generally I am selecting the option to "Exclude dependent packed libraries" in my build specifications, but if I leave that unchecked it will open properly (because it places the dependency directly next to where it is built). I did not have these issues until I placed my shared components into vi.lib, so I would be grateful for any help to help me debug this!
  7. I think I am comfortable with the idea of creating packages and putting into vi.lib - that is a good idea except there is one dependency library that is a little different. The one that I am not sure about is a plug-in type that loads the correct child plug-in based on the configuration file for the application. So for that one I would still need to do a little directory trickery. I will do a little playing around and see what I can get to work (and I will try to remember to reply back with how I handled it).
  8. For a lot of my LabVIEW projects, I have been developing scripting tools to help team members get to a good starting point for their code or to remove human error when following templates. After seeing Becky Linton's presentation at NI Week in 2016 (link), I was inspired to use Project Templates to make it a little easier for the developers to get to. I have been able to get it to work to varying degrees at this point, but I have a question on how to handle project-specific dependencies. If I have a team working on a larger development project that has shared core code and we have it in a repository, everyone on the team usually puts the cloned source on a different location on disk. If my scripting tools have a dependency on code in that repository (class ancestor is biggest), then its location would move from development machine to development machine. Therefore, if I put my tools into the LabVIEW\ProjectTemplates directory, those dependencies would need to re-map for every user and that defeats the benefit to having it be a part of the Getting Started window - at that point it is easier just to point them to the scripting wizards that are pulled with the rest of the code from the repository. Does anyone have a good suggestion for how to accomplish a good structure with project-specific dependencies? Or am I trying to fit a square peg into a round hole for this type of application?
  • Create New...

Important Information

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