Jump to content

Package version bug in 2010

Recommended Posts

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.

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...

Important Information

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