Jump to content

Ashish

JKI Team
  • Content Count

    289
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by Ashish

  1. You can think of adding a dummy subVI in the package that you will replace later.
  2. James, There are no reports of VIPM update checker. The JKI Update checker should have notified you of the build 1967. Chances are that the update checker might have been blocked possibly by firewall resulting in this behavior. Sorry for the inconvenience.
  3. Anders, The error image seems to be missing. Can you send it again? Also, send the error description, image to support@jki.net.
  4. If you add other packages as dependencies, then you will get all the necessary subVI components installed. Also, the order of installation should not matter since VIPM performs mass comipile after package installation.
  5. Well....sorry to say that we are not able to recover the missing attachment. We will keep an eye on the error occurrence in future and let you know how it goes.
  6. Hi, There seems to be no easy way to find the missing attachment. Do you remember the name of the attachment? I can check on my local machine, if I had ever downloaded it.
  7. Ok. Let me check with our team about the missing attachment.
  8. Hi, Is the issue resolved? If not, can you share the code to help reproduce the behavior?
  9. Steen, Just trying to catch up on open items. Have you ever resolved the issue? Do you happen to have any dynamic libraries?
  10. Manikandan, This thread is not relevant for licensing related discussions.
  11. Sara, This article will provide appropriate reasoning: http://support.jki.net/entries/66745297-VIPM-2013-cannot-install-packages-built-in-VIPM-2014
  12. Sara, So, as suggested in the message, did you try building with System target? We introduced "System" as a target in order for users like you to create packages without VIs in it.
  13. Good catch! I did not pay attention to the error and certainly recommend the way you did. Thanks for the updates.
  14. Jason, Thanks for the updates and clarification. Glad to know that you were able to sort it out.
  15. Attached is the screenshot showing updated VI that should work. Let me know how it goes.
  16. Is your issue resolved? If not, is VIPM connected to internet? Refer this article and let me know how it goes: http://support.jki.net/entries/20589198-Solving-VIPM-Network-Connection-Issues
  17. Isaac, Let me tell you that your English is perfectly fine. I was not able to reproduce the behavior on my Win 7 64 bit LabVIEW 2014. It needs to download the package. Is your VIPM connected to internet? Have you tried installing any other package?
  18. Try to open the .vip file with "VIPM File Handler.exe". Attached is the link for detailed explaination: http://screencast.com/t/kFWwBQ3Diqp
  19. Thanks for posting your observations.
  20. Sree, You can use VIPM to distribute EXE files. Now, it all depends how you setup the architecture to make a plugin architecture for your custom EXE. Yes. For accessing private Repo, user will need VIPM Pro.
  21. Steen, We were not able to reproduce the behavior. We tried using the available packages in VIPM and setting up the dependency for version mismatch. Package was built successfully and during the package installation, we received the message to update the dependent package and that was also installed successfully. Can you help understand your scenario better?
  22. Thomas, We were able to reproduce the behavior and recorded it as Case 16585 for consideration to be fixed in future. We will notify you when we have the fix. Till then, sorry for inconvenience.
×
×
  • Create New...

Important Information

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