I've set appsync update parameters into the package.ini file to update and installed app deployed as a .msi. The update works fine, as i can see the changes in the app. However, when i go to check add/remove programs support info on the thinapp, I noticed the version number hadn't changed. Why is this so? If I don't use appsync, and instead deploy an updated .msi to overwrite the installed app, the version number does increment with what i've defined in the package.ini.
By default when you are doing AppSync is the new version not being reregistered with thinreg. Therefore will no update happen to the Add and Remove Programs. But you can tell AppSync to perform a thinreg when the update is finished. You do so by placing thinreg.exe (can be found in the Setup Capture folder) in your AppSyncURL location, just next to the updated package.
In order for this to work must you already have registered the old version of the package on your client. You probably have done this since you say you have deployed it with the help of our MSI and that is using our thinreg.exe.
Placing a copy in the same location as your updated package should do it. I just verified it myself using ThinApp 4.6. In my test was my AppSyncURL located on c: drive in other words using file:// and not http://. What are you using as AppSyncURL? I registered my original version of the package with thinreg.exe manually and not via MSI. Please try this approach as well, just as a troubleshooting step. Using our generated MSI or thinreg.exe standalone should not be any different.
Just to make sure, the two packages have different inventory names in package.ini I assume.. It's the inventory name we use in Add/Remove programs.
when i run thinreg manually after the update occurs, it does update the entry in add/remove programs. Is there some parameter that I can define in the package.ini file to run the update and run thinreg? I don't know how else to get this to work automatically.
I have now investigated this some more.. It seems like if you manually copy the packages to the client and register it with the help of thinreg.exe and then do AppSync with thinreg.exe available in the AppSyncURL will it all work as expected. It seems to not be the case if you have used MSI as your delivery mechanism. Why this is so do I not know, but I have made the developers aware of this behavior and are awaiting their response.
In the meantime please have a look at this video I just posted: http://vimeo.com/channels/thinapp#20324119
It shows you the functionality and since I ran through the process could I just as well record it.
It works as expected when manually registering the first package with the help of thinreg.exe (as shown in above video).. It only fails if you use MSI to deploy you first package.. Looks like engineering are made aware of this and are investigating the issue..