Version Control
Version Control
We are currently shipping our product with Amyuni 2.10i-8. This version has worked very well with one main exception. When other products are installed that use an older version of the Amyuni Converter, it overwrites the driver and our product ends up with this older version as well. Our support is spending endless hours helping our customers clean out these older drivers so that 2.10i-8 can be re-installed. We would upgrade to Amyuni 2.50 if we were sure that it would solve the problem. Your input would be appreciated.
Hello,
Different versions of the PDF Converter are installed seprately. Which means if you have version 1.5, 2.0, 2.10 and 2.50 on a given system, each of these versions will install and use a separate driver and a separate version of CDIntf.
If you have version 2.10i-8 and 2.10a lets say, these two version being 2.10 will install and use the same driver and the same version of CDIntf so it is advisable in this case to install the oldest version than the newest one to the newest version of the driver and of CDIntf will overwrite the old one.
Hope this helps.
Different versions of the PDF Converter are installed seprately. Which means if you have version 1.5, 2.0, 2.10 and 2.50 on a given system, each of these versions will install and use a separate driver and a separate version of CDIntf.
If you have version 2.10i-8 and 2.10a lets say, these two version being 2.10 will install and use the same driver and the same version of CDIntf so it is advisable in this case to install the oldest version than the newest one to the newest version of the driver and of CDIntf will overwrite the old one.
Hope this helps.
Version Control
The problem we run into is:
We install (for example) version 2.50f with our product.
Then another program installs version 2.50a.
Now both programs have 2.50a.
If there were problems with 2.50a then our users have to re-install 2.50f on every machine that has 2.50a. Is there a way to avoid this? Should Amyuni check the version during installation and not allow an older version to overwrite a newer one?
We install (for example) version 2.50f with our product.
Then another program installs version 2.50a.
Now both programs have 2.50a.
If there were problems with 2.50a then our users have to re-install 2.50f on every machine that has 2.50a. Is there a way to avoid this? Should Amyuni check the version during installation and not allow an older version to overwrite a newer one?
Since all drivers you are installing are 2.50, it is expected that the latest installed driver overwrites the new one.
A possible workaround will be to ask your users to install your application after installing other applications or to install the application that has the neweset driver version at the end.
As far as I know, checking which version is getting installed is no possible, i will double check this however.
A possible workaround will be to ask your users to install your application after installing other applications or to install the application that has the neweset driver version at the end.
As far as I know, checking which version is getting installed is no possible, i will double check this however.