Jump to content

Search the Community

Showing results for tags 'base path'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Special Interest Boards
    • Developing LabVIEW Tools and Add-ons
    • Professional User Interface Design in LabVIEW
  • VI Package Manager (VIPM)
    • VI Package Manager (VIPM)
    • Dragon Beta
  • JKI Tools
    • JKI Flat UI Controls
    • JKI Design Palette
    • JKI State Machine
    • JKI State Machine Objects (SMO)
    • Caraya Unit Tester
    • VI Tester
    • JKI JSON
    • HTTP REST Client
    • JKI Simple Localization
    • EasyXML Toolkit
  • Legacy Tools
    • Legacy Tools
  • VIPM Community Add-ons for LabVIEW
    • JSONtext by JDP Science

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. I have a TestStand tool I want to deploy and it uses a few LabVIEW VIs as well as a sequence. Is there another tool for TestStand packages that anyone is aware of? The goal is to deploy to <TestStand Public>\<TestStand Version>\My Folder here. If VIPM could offer the two base paths and assume that the LabVIEW version selected is also the TestStand version to deploy, then it all works seamlessly and I can build a 2017 version and it can upgrade on deployment/install. I have to attempt a work around for the moment. Install my sequence and code to a temp ProgramData folder. Run a custom action after the package install to find/detect which LabVIEW version and test stand version, copy the content over and mass compile, add to the TestStand Tools menu all while keeping a log... Uninstall would need a custom action to also remove it and utilize the log on install. Open to other thoughts and open discussion! Thanks.
×
×
  • Create New...

Important Information

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