The version information comes from the program installed and is grabbed during install.
You could reverse engineer it and search the registry key (most likely under MSI install path) or you could also just go in the SQL Database and update the version there.
Updating the SQL DB is at your own risk as support often says that modifying the tables directly is not safe.
Curious though, why did you package the apps together and not individually? Packaging them together will prevent you from updating a single app, you'll have to update the whole package any time one of the apps change...
yes, I already changed the version number in SQL db, but I think this is not how it is intented.
I am using the approach to create application packages for a department or user group that need the same bundle of apps.
When there is a requirement to update one or more applications the whole application bundle will be updated and published, the old will be retired then after testing.
Thanks to the new states of packages coming with AV4
Glad you like the new package lifecycle states.
In this particular use case of stacking apps, it would make sense that the package version is editable as a text field during packaging. Please note that the .json file along side the vhd/vmdk file will also still contain the version number finalized during packaging.
I am really glad you are enjoying App Volumes!
While modifying this particular field in the database may be benign, unfortunately we cannot recommend editing the SQL database, as this can often lead to issues if not done properly. Modification to the database may also inadvertently cause compatibility and support issues in the future as our developers will not anticipate the database being modified directly by the administrator.
Thank you again for your interest in the product. I will pass on your excitement to the team!
our whole team loves app volumes since years now
Will mark your last answer as correct, because this is what matters to the customer and for us as a service provider.
Just updated to AV4U1 (VMware App Volumes 4 Update 1 Release Notes) in our lab. We were also struggling with packaging Chrome the last weeks