In previous chapters you have learned about ThinApp basics; how to create a package and how to deploy a package to your end users. Now, it's time to learn how to maintain a package. An application's life cycle includes updating the application to a new version or changing its settings. In this chapter you will learn about the following topics:
- The most efficient update method for different update needs
- How to use the
sbmerge.exetool to update a project folder - Different sandbox considerations when creating a new version of a package
There are different categories of updates. Different update methods are preferred for different update categories. That said, a certain update mechanism may be the most efficient in a certain update scenario but can very well still be used in another. The different update categories are:
- Major updates (that is, full version updates): This update category is typically a major product version update. For example, Microsoft Office 2007 was updated to Microsoft Office 2010.
- Minor updates (typically point releases or service packs): This category typically features updates and bug fixes within a specific full version. For example, updating from Adobe Acrobat Reader 8.0 to 8.1. Both are within the full version of 8.
- Patching and hotfixes: These updates are typically smaller in size than minor updates/point releases but are essentially within the same update category.
- Configuration changes: Configuration changes are typically a very small number of changes. These are often only a couple of registry changes or a change to a
.inior configuration file. - ThinApp runtime updates: There is rarely any need to update the ThinApp runtime within a package that is deployed and fully functional. The only reason to update the runtime would be to inject new operating system support or to update the license key in an existing package.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.