Daklu Posted August 10, 2010 Report Share Posted August 10, 2010 So I was playing around with building packages in VIPM 2010 and I ran across a bug in the package versioning. The package version number contains the build number except for the very first time the package is built. That package has the build number 0 removed. This appears to confuse VIPM with respect to which version is the most recent. More recent builds with the same Major.Minor.Bugfix numbers aren't consistently identified as an update. Even though I have the most recent version installed, the icon on the left indicates an upgrade is available. Selecting Upgrade... from the context menu prompts me to install v1.0.0. The Action column in the dialog box does correctly identify it as a downgrade though. Link to comment Share on other sites More sharing options...
Michael Aivaliotis Posted August 10, 2010 Report Share Posted August 10, 2010 Thanks. Will investigate further. I've added it to our internal tracker as Case 9640. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.