Jim Kring

  • Total activity 69
  • Last activity
  • Member since
  • Following 0 users
  • Followed by 0 users
  • Votes 7
  • Subscriptions 23


Recent activity by Jim Kring Recent activity Votes
  • Managing Package Dependencies

    OK, you've gotten through all the basics of package building and your ready for the advanced stuff.  Now, let's learn about package dependencies. First, what is a dependency?  Basically, its someth...

  • Using VI Package Builder with Source Code Control

    Now that you know all about Managing Package Dependencies and Package Configuration Management you'll probably want to know how these features can work with your Source Code Control (a.k.a. Softwar...

  • Package Configuration Management

    Now that you've finished learning about Managing Package Dependencies you'll want to know about Package Configuration Management.  But, what does "configuration management" mean, exactly?Simply put...

  • Error Code 54 when checking for package updates

    VIPM Versions Affected All versions -- the problem is not VIPM version specific. Problem VIPM is unable to download packages and you see following error.   Solution (Windows) Check the proxy setti...

  • Solving VIPM Network Connection Issues

    Note: In VIPM 2012 We made some changes to the underlying code that fixes a long standing connection issue reported by many users. If you are having network connection issues, It's highly recommend...

  • Deactivation Fails for Licensed Add-ons built with VIPM

    VIPM Versions Affected VIPM 2014 through VIPM 2018 (builds 2020 and earlier are affected) Fixed in VIPM 2018f1 Issue When users attempt to deactivate an add-on that was built using VIPM (with licen...

  • How to use Licensing and Activation in Your LabVIEW VI Packages

    This video walks you through the process of how you would add license and activation to your built LabVIEW VI package. You can also find more information here. This feature is available in VIPM Pro.

  • VIPM 2013 cannot install packages built in VIPM 2014 or greater

    Problem: If you are using VIPM 2013 or older and you try to install a package built with VIPM 2014 or greater, you will get a message similar to the one shown below: This is because VIPM 2013 d...

  • VIPM 2017 f1 Release Notes

    Note: Other release notes can be found here. What's New in VIPM 2017 f1 VIPM 2017 f1 is a Maintenance Release with bug fixes -- see VIPM 2017 Release Notes. It is recommended that all VIPM 2017 us...


    General Operation The VIPM VI-based API is a collection of VIs that allow you to command and control VIPM (VI Package Manager). The VIs have been compiled in LabVIEW 2009 and can be used for autom...