![]() |
|
#1
|
|||
|
|||
|
There must be an easier way of doing this.
I find that if I wrap a program with Armadillo, then use SB6 to add a manifest, the program crashes at runtime with an Armadillo Unpack Exception message. The sequence I seem to need to follow is: 1. Compile Clarion app 2. Create dummy SB6 installer. The purpose of this installer is just to embed a manifest into my app. 3. Compile dummy installer Then run dummy installer to install app to a temporary directory. 4. Use Armadillo to wrap the app that now has the manifest within it. 5. Sign the app 6. Create 'real' SB6 installer to install manifested/wrapped/signed app and support files. Friedrich, is there some way to script this? To run a batch file after the manifest has been embedded so I can have that call Armadillo? Or if I pause the setup script, is there a temp directory where I'd find my app after the manifest has been inserted? Jane |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Information Please | NewsArchive | SetupBuilder - NNTP | 9 | 12-21-2006 03:38 AM |
| Clarion 6.3, SetupBuilder 6 and Vista | NewsArchive | SetupBuilder - NNTP | 5 | 11-18-2006 04:23 AM |
| SetupBuilder and Windows Vista [October 28, 2006] | NewsArchive | SetupBuilder - NNTP | 26 | 11-01-2006 04:34 AM |
| Version manifest test | NewsArchive | SetupBuilder - NNTP | 5 | 05-29-2006 12:14 AM |
| SetupBuilder 5 and Windows Vista (Beta 1) | linder | SetupBuilder | 0 | 08-09-2005 08:03 AM |