Jump to content

HB65093

Members
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About HB65093

  • Birthday December 8

Profile Information

  • Gender
    Male
  • Location
    Houston, Texas
  1. Our company continued our VIPM licenses last year and most of them are about to expire. However, since JKI has NOT released any new versions (fixes, improvements, etc.) since before our last year's upgrade, it appears any future purchase would likely be another waste of money? Please let us know if JKI is has decided to stop new development, bug fixes and enhancements for VIPM. Thanks & Regards, James
  2. Our company continued our VIPM licenses last year and most of them are about to expire. However, since JKI has NOT released any new versions (fixes, improvements, etc.) since before our last year's upgrade, it appears any future purchase would likely be another waste of money? Please let us know if JKI is has decided to stop new development, bug fixes and enhancements for VIPM. Thanks & Regards, James
  3. I hadn't worked on this issue until today and found I need data for the Post-Install custom Action.vi Is the Package Version available in the Variant data? If not, is there a way to get this information programmatically? Thanks for any suggestions. James
  4. Jim, I don't have that option checked, however, that wouldn't correct the issue I am trying to address. If I Un-Publish or Deprecate a package from the Repository Manager I would expect that end users would not be able to use or re-install that package. However, since the right-click menu (list of packages) is built from package versions in the cache directory, any packages they have previously installed remain visible and can be re-installed from the cached copy. So, if I have a package version that had a critical bug, I cannot make certain that it is no longer used by simply using Un-Publish or Deprecate. I guess I'll try creating a post install action to delete all previous package versions from the cache directory. Thanks for the response. James
  5. When I un-publish or deprecate a package I would expect that it would not be visible to the end users to select for install. However, after first trying deprecate and then Un-Publish I learned that they are all still on the list of "Install Other Version" found by right-clicking on a package. Even worse, I learned that these packages (Un-Publish & Deprecate) are all still available to the user since copies remain in the ProgramData (C:\ProgramData\JKI\VIPM\cache) directory. So, I need recommendations on the best practice to remove these (Un-Published & Deprecated) versions from the right-click listing and the best process to use for deleting them from the cache directory. From testing, I learned the right-click menu is created from the cache directory. And, I should be able to delete cached versions with a post install action. However, this will mean continually modifying my post install action VIs every time I deprecate or un-publish a version of one of my packages. I'm hoping there is an automated method/setting I have overlooked that deletes deprecated & un-published versions from the local cache. Thanks and regards, James R. Jones Halliburton Energy Services
  6. OK, Thanks Ashish. However, it's bad that VIPM returns "Your software is up to date" dialog if the check were blocked by a firewall.
  7. I was fighting a bug related to a problem that had already been corrected, but didn't realize I didn't have the latest version installed because Check for VIPM Update reports I have the latest version. Installed version: 2014.0.0 (build 1941) Apr 22 2014 Available at JKI: 2014.0.1 (build 1967) Oct 10 2014 Is there a bug with the process of checking for updates or has this release not been made public. I wasted a lot of time this morning before I realized the problem and downloaded/installed the latest release. Regards, James R. Jones
  8. Ashish, I wanted to let you know the issue I encountered was NOT with my version of VIPM, but related to my use of sub-VIs in my Post-Build VI. In addition, I modified my process to use a Post-Install action instead of the Post-Build to acheive the desired functionality. I didn't upgrade my Package Manager as I assumed it was related to my process or VIs; it just took a while to isolate the root cause of my issue. Thanks for the feedback that gave me the confidence to find MY programming error. Regards, James
  9. This is my first attempt to use a Post-Build Custom Action 1) I used the Generate VI button to create the shell VI 2) I added some very simple code to find/set a VI attribute to read-only During the build I received this error and don't know what to do next? " Error 15 occurred during the Build: Post-Build step. Possible Reason(s): (Script VI could not be opened) 13967F6905F236670976AD1488E1267A in VIPB_API.BuildAndPackageLibraryFromSpec[Private].vi " Any suggestions would be appreciated. Regards, James VIPM 2014.0.0 (build 1941) Apr 22 2014 Email me
×
×
  • Create New...

Important Information

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