Jump to content

Bob

Members
  • Content Count

    2
  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. A customer has reported similar behavior with VIPM 2012.0.1 and LabVIEW 2011 64-bit. The facts as reported to me: System has both LabVIEW 2011 32-bit and 64-bit versions installed VIPM has no issues connecting to and installing packages for LabVIEW 2011 32-bit When verifying the connection to LV 2011 64-bit, LabVIEW closes, restarts, and VIPM times out with an error before the splash screen is displayed. Uninstalling and reinstalling LabVIEW did not resolve the issue and VI Server settings were checked and appeared to be correct The solution was to rename the LabVIEW.ini file as you describe above. I've attached a copy of the bad .ini file to use when troubleshooting this further. -RDR OLD_LabVIEW.ini.zip
  2. Issue: When building a LabVIEW shipping example with a variable library (lvlib containing only variables), the lvlib is not included when I build and install the package to the Examples folder. I've attached example code demonstrating this behavior. Steps to reproduce: In LabVIEW Create a new project Add a library Add a variable to the library Save the project and library In VIPM Package Builder Create a new package Point to the folder where the project and lvlib are stored Set the destination in 'Source file settings' for these files to the Examples folder Build the package In VIPM main window Install package Open Examples folder and notice the lvlib is missing. This also occurs if you set the destination for Toolkit VIs, and I imagine other locations won't work either but I did not test for them. Workaround: Add a VI to the variable library and VIPM Package Builder will not ignore the lvlib file. Cheers! -Bob dev.zip
×
×
  • Create New...

Important Information

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