Recently I was asked if the ThinApp SDK can be utilized to force an AppSync update on a ThinApp Package. More importantly, some customers have wanted to know if it was possible to change the AppSync URL on the fly.
So….I thought I’d share this script. 🙂
Very simply, this VBScript uses the ThinApp SDK to attach to the original package and conduct an AppSync Update to it with a specified “newer” package.
This ONLY requires a couple of things…
- THINAPPSDK.DLL is registered on the system where the script is executed.
- The old ThinApp Package (TAOldPackage) is accessible to the system/user running the script.
- The new ThinApp Package URL (TANewPackageURL) is accessible to the system/user running the script.
- This code should be executed natively. The application may be left running while the Application Sync update is performed (this goes for both the ThinApp SDK and APPSYNC.EXE), however, the user must close and reopen the application in order to see the update (same as with a ThinApp Side-by-Side update).
Technically, one could put the script into a ThinApp package of it’s own, but this might be a little convoluted…and definitely need testing. The interesting (and somewhat crazy) thought here is the script could do the AppSync with a ThinApp package vs the actual Package AppSync settings (found in the PACKAGE.INI) and the script could be used to also perform search validation for an updated package based upon whatever validation logic defined. But this is all “Crazy Talk” here….so remember, test, test, Test! 🙂
Ohh….and none of the ThinApp packages need AppSync configured prior to this. It just works. 😉