Stand-a-lone package
I've searched through the forum here; and maybe I'm just not searching correctly, but I'm trying to find a way to wrap up a program so that it is a "stand-a-lone" installation.
Basically I'm looking at wrapping up a package so that there is only one EXE and everything is inside of that EXE. This way it can be installed on a workstation that does not have any connection to our companies network. (Package is deployed via a CD or Thumbdrive)
We are using Wise Package Studio Build 6.1.0.281
I know I've come across this before, but I haven't been packaging any applications for almost a year now (I went on to do strictly VBScript since we already had a few individuals packaging up our software, but now we are back to just one individual packaging our software, so I'm trying to get back into it); we are wanting to package some of the software up into one exe without the need to retrieve any files from our servers.
I'm currently trying to test this out on a VBScript I created, which only requires the script itself (trying to make the first one as simple as possible), and this way the script can be deployed to our workstations without the problem of anyone editing the script.
Can someone point me in the right direction?
Basically I'm looking at wrapping up a package so that there is only one EXE and everything is inside of that EXE. This way it can be installed on a workstation that does not have any connection to our companies network. (Package is deployed via a CD or Thumbdrive)
We are using Wise Package Studio Build 6.1.0.281
I know I've come across this before, but I haven't been packaging any applications for almost a year now (I went on to do strictly VBScript since we already had a few individuals packaging up our software, but now we are back to just one individual packaging our software, so I'm trying to get back into it); we are wanting to package some of the software up into one exe without the need to retrieve any files from our servers.
I'm currently trying to test this out on a VBScript I created, which only requires the script itself (trying to make the first one as simple as possible), and this way the script can be deployed to our workstations without the problem of anyone editing the script.
Can someone point me in the right direction?
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
turbokitty
17 years ago
Well, running a vbs script probably isn't the easiest example of a setup.exe. You'd need to create a custom action that calls the VBS and then you'd have to sequence the custom action.. all a bit ugly in Wise.
Basically you just create your package, using the repackager or by building it manually, then be sure you build a setup.exe at build time.
That said, I recommend against creating a setup.exe. You should create an MSI and at build time, build the files within the MSI (internal cab file). Then you have one file to call. Just use msiexec /i "file.msi" /qn to run it
Basically you just create your package, using the repackager or by building it manually, then be sure you build a setup.exe at build time.
That said, I recommend against creating a setup.exe. You should create an MSI and at build time, build the files within the MSI (internal cab file). Then you have one file to call. Just use msiexec /i "file.msi" /qn to run it
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
