Simon Posted July 20, 2011 Report Share Posted July 20, 2011 [EDIT] Forgot to include system details; - Win XP SP3 - Labview 2009 - VIPM 2010 (2010.0.2) Proffesional [/EDIT] After upgrading to VIPM2010 from VIPM 2009, we are now unable to upgrade our own "Unpublished" packages (built in-house). The VIPM 2010 Package Action Confirmation window even fails to display the name of the package properly as can be seen in the attached image. the name is displayed as "pmech_lib_80 v01" while the actual package name should be something like "pmech_lib_80-01_advanced_strings v1.2.12-1". VIPM2010 seems to be parsing everything after the first '-' as a version number, but it's not the case here. Our naming convention (which is important for us to keep as is) has been working just fine with previous versions of VIPM. We upgraded to VIPM2010 because we couldn't upgrade the OpenG packages. Any help or ideas would be greatly appreciated. Link to comment Share on other sites More sharing options...
Michael Aivaliotis Posted July 21, 2011 Report Share Posted July 21, 2011 There is an issue in VIPM 2010 where you cannot have a dash (-) in the package name. The only workaround right now is to not use dashes in the package name. We are working on fixing this in the upcoming release. Sorry, I can't be more helpful. Link to comment Share on other sites More sharing options...
Michael Aivaliotis Posted September 15, 2011 Report Share Posted September 15, 2011 Were these packages built with VIPM or OpenG Package Builder? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.