Jump to content


JKI Team
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Ashish

  1. Manikandan, This thread is not relevant for licensing related discussions.
  2. Sara, This article will provide appropriate reasoning: http://support.jki.net/entries/66745297-VIPM-2013-cannot-install-packages-built-in-VIPM-2014
  3. 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.
  4. Good catch! I did not pay attention to the error and certainly recommend the way you did. Thanks for the updates.
  5. Jason, Thanks for the updates and clarification. Glad to know that you were able to sort it out.
  6. Attached is the screenshot showing updated VI that should work. Let me know how it goes.
  7. 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
  8. 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?
  9. Try to open the .vip file with "VIPM File Handler.exe". Attached is the link for detailed explaination: http://screencast.com/t/kFWwBQ3Diqp
  10. Thanks for posting your observations.
  11. 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.
  12. 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?
  13. 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.
  14. Steven, I will recommend you to contact TortoiseSVN Support (http://tortoisesvn.net/support.html). This forum is primarily for JKI Products (jki.net/products).
  15. Please try to mass compile the source before building the package. Let me know how it goes.
  16. Please try to uninstall the package, restart PC and install the package again. The fact that you installed LabVIEW 2010 and 2012 after the installation might be the cause of this issue.
  17. No worries. Thanks for providing all your observations.
  18. I was not able to reproduce the behavior. Attached is the screenshot of all the versions as stated in the package i.e for LabVIEW 2009 to LabVIEW 2013 Not sure why is the issue? Try with "Run as administrator" option that you get from right mouse click.
  19. We want you to try to re-install VIPM. To do this you will have to uninstall VIPM using the VIPM uninstall and then delete the following folders manually: C:\ProgramData\JKI\VIPM C:\Program Files (x86)\JKI\VI Package Manager Let me know how it goes.
  20. Thomas, Ok. So, you are concerned about the top level VI searching for VIs after package installation and you are thinking that it will possibly link to wrong VIs. Typically VIPM should mass compile after package installation in order to ensure that the newly installed package is linked correctly. Do you see "mass compiling" in the VIPM status bar at the bottom during package installation?
  21. What I understand is: after installation, the Top Level VI links to the newly installed VIs under vilib and provides warning about the new linkage. Is that correct? Also, it seems that building 2 packages is also linking correctly to the installed VIs under "..\..\..\..\..\..\MyProject.." Can you help clarify the issue?
  • Create New...

Important Information

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