A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize request, please see:
We finally shipped this app today. One major downside for this app will be that the Latest version will not be able to tell if a previous LTR release is installed and will update an LTR install to the latest version. That being said, if your entire site is using either the Latest or the LTR exclusively, there should be no issues. We also discovered that installing a newer version will not uninstall a previous version, so we included a script to perform that uninstallation as well. The LTR releases from Patch My PC should be able to validate that an existing LTR version is installed successfully, but we are going to treat each major LTR release as it's own product (LTR 3.22 is it's own product and when LTR 3.28 is released, we will make a new product with LTR 2.38).
I am working on this product now, for those interested, I have noticed that installing a newer version does not remove the previous version. How should we handle this by default? I am assuming we should remove the previous version of the software when updating.
Unfortunately not yet, it is in big letters on a sticky note on my monitor though! What we may end up doing is adding both LTS and non-LTS versions then allowing the customer to choose which they want to update if we cannot find a way to differentiate them programmatically.
I have looked at this and still don't have a great solution, but am not ready to mark it as a no-go yet, as I know this is an important product for many. I will put it on my schedule to take another look at it this month.
I noticed on the Zotero thread, it was listed as incompatible, because they don't know how to properly versioning their Windows binaries. However, QGIS does not either. For my custom QGIS installer, I have to use the current SHA256 hash of qgis-bin.exe to add to my detection code.
Still working on this one. The biggest issue is actually ensuring we don't upgrade LTR releases to non-LTR releases. They have a weird release schedule so making rules to target LTR/nonLTR releases is the hold-up here.
Brilliant, thanks again for all your help on this one.
We finally shipped this app today. One major downside for this app will be that the Latest version will not be able to tell if a previous LTR release is installed and will update an LTR install to the latest version. That being said, if your entire site is using either the Latest or the LTR exclusively, there should be no issues. We also discovered that installing a newer version will not uninstall a previous version, so we included a script to perform that uninstallation as well. The LTR releases from Patch My PC should be able to validate that an existing LTR version is installed successfully, but we are going to treat each major LTR release as it's own product (LTR 3.22 is it's own product and when LTR 3.28 is released, we will make a new product with LTR 2.38).
Awesome, thanks Andrew
Yes, we can include a prescript, we do similar with Java. Awesome. I hope to have this product added by the end of the month.
Hi Andrew, yeah ideally removing the old version as part of the update would be great. I guess a pre script if possible?
I am working on this product now, for those interested, I have noticed that installing a newer version does not remove the previous version. How should we handle this by default? I am assuming we should remove the previous version of the software when updating.
haha, understand. thanks for the response.
Unfortunately not yet, it is in big letters on a sticky note on my monitor though! What we may end up doing is adding both LTS and non-LTS versions then allowing the customer to choose which they want to update if we cannot find a way to differentiate them programmatically.
Hi Andrew, did you manage to find some time to look at this again? thanks
I have looked at this and still don't have a great solution, but am not ready to mark it as a no-go yet, as I know this is an important product for many. I will put it on my schedule to take another look at it this month.
Hi there, wondering if there is an update on how this is going, will it go ahead?
I noticed on the Zotero thread, it was listed as incompatible, because they don't know how to properly versioning their Windows binaries. However, QGIS does not either. For my custom QGIS installer, I have to use the current SHA256 hash of qgis-bin.exe to add to my detection code.
Hi Andrew,
Thankyou for the update. i hope this can be resolved soon. :)
Still working on this one. The biggest issue is actually ensuring we don't upgrade LTR releases to non-LTR releases. They have a weird release schedule so making rules to target LTR/nonLTR releases is the hold-up here.
Hi, i was just wondering how this is going?
This is how i go it going.
We'll look at this for April 2021
Is there any updates?