Jump to content


RDR

Member Since 17 Dec 2013
Offline Last Active Jun 21 2016 04:19 PM
-----

Topics I've Started

VIPM Tools Menu Entry Does Not Appear

21 June 2016 - 04:21 PM

This may be intentional behavior, but I noticed after installing a new version of LabVIEW on my system the Tools menu entry for VI Package Manager did not show up until after launching VI Package Manager.  It appears you're creating the files during VIPM start-up and not during installation?  Is this intentional?

 

-RDR


Error 1 reported when using Publish Packages to Repository.vi from VIPM API

04 May 2016 - 03:45 PM

When using the Publish Packages to Repository.vi from the VIPM API I am receiving the following error text:

 
10:27:19.871 AM 5/4/2016 Error  1 at VIPM API_vipm_api.lvlib:Parse String Array Message_vipm_api.vi<ERR>
Code:: 1
Source:: (Invalid URL) E6C7850DB8DC443245FEA289ED5599DC in OGPM Class.lvlib:2298EAB45C3ADB6BA393ADD20A1567B2->Repository.lvlib:E4BDF9BD7B76EC63B78E078A2430E6BE->Repository.lvlib:412A7FE00073B5B996D6EC522E780BF5->VIPM API.lvlib:5F6CC0C4C5DFEC614D6E5B026429AAF0->2EDC3C81B4A2C6C7E1F2041B75CF3851->VIPM Main Window.vi 
 
This is code we've not changed at all--the error started to show up recently and we can reproduce this on multiple machines.  Some have VIPM 2014 and others VIPM 2015.  Do you have any recommendations for what to try next in debugging this error?
 
Thanks,
 
-RDR
 

Bug: Use of the package Install Requirements for LabVIEW Bitness does not work as expected

17 December 2015 - 03:42 PM

When selecting to build a package for only LabVIEW 64-bit, the package is still displayed in my repository when installing to 32-bit LabVIEW.  I noticed in the spec file for the packages there is a tag for:

Exclusive_LabVIEW_System="ALL"

 

I assume this is the value intended for 32 or 64-bit LabVIEW, but I do not see this tag update no matter what changes I make to the LabVIEW bitness.

 

I am using the latest version of VI Package Manager Pro (2014.0.2).

 

Kind regards,

 

-R


Bug: Use of the package Install Requirements for LabVIEW Bitness does not work as expected

17 December 2015 - 03:42 PM

When selecting to build a package for only LabVIEW 64-bit, the package is still displayed in my repository when installing to 32-bit LabVIEW.  I noticed in the spec file for the packages there is a tag for:

Exclusive_LabVIEW_System="ALL"

 

I assume this is the value intended for 32 or 64-bit LabVIEW, but I do not see this tag update no matter what changes I make to the LabVIEW bitness.

 

I am using the latest version of VI Package Manager Pro (2014.0.2).

 

Kind regards,

 

-R


Bug: Use of the package Install Requirements for LabVIEW Bitness does not work as expected

17 December 2015 - 03:41 PM

When selecting to build a package for only LabVIEW 64-bit, the package is still displayed in my repository when installing to 32-bit LabVIEW.  I noticed in the spec file for the packages there is a tag for:

Exclusive_LabVIEW_System="ALL"

 

I assume this is the value intended for 32 or 64-bit LabVIEW, but I do not see this tag update no matter what changes I make to the LabVIEW bitness.

 

I am using the latest version of VI Package Manager Pro (2014.0.2).

 

Kind regards,

 

-R