I've been wanting a GUI driven SBMerge utility for quite a while now so I built one after my client wanted it due to slow typing skills. If your a slow typist this is built for you! From now on you can avoid the CMD prompt as much as possible as the hunt and peck method isn't your friend. For myself, and even some people with fast typing skills should still find this GUI driven wrapper faster than using the CMD prompt, along with the added feature of logging each task along the way.
As for the SBAssist, You should find the GUI use of this application easy to use, almost too simplistic. The install is a simple file copy to the ThinAppBuild folder. After that is completed you can run it by simply clicking on it when needed.
Keep in mind the this tool simple creates a GUI Wrapper that still uses SBMerge.exe underneath it does not replace it. All best practices of using SBMerge.exe should still be observed. If you are not familiar with those please see the link below
http://blogs.vmware.com/thinapp/2010/02/simple-steps-for-using-sbmerge.html
Delete or rename existing Sandbox for the application you plan on making changes to, this will make sure the application has a clean Sandbox.
Ready Set Go
PreSteps
1. Close all application possible if opened.
2. Delete current sandbox!
3. Take a backup of the Build directory prior to using SBMERGE or SBASSIST
Start your SBMerge session.
- Launch ThinApp’ed application and make changes as needed. including updated registry settings, update to program, etc.
- Close Application,
- Verify sandbox is not in use. If so a reboot of the VM might be required to close the locked files. This should not affect the SBMerge
- Run SBAssist tool.
- Select SandBox folder|
- Select the project folder
- Verify Information, if correct the App will run the command to generate a text file from SBMerge Print followed by Apply. OR If you didn’t backup of the Build directory prior please do this first!
- A logfile is created in the ProjectDir of the application along with a overview logfile in the ThinApp build folder.
- Run build.bat manually
- Test application!
Enjoy,
Kevin E. Komlosy
VirtuallyTangled