Embedding other installers - Revision history

65.210.121.6: Undo revision 21808 by 192.162.19.21 (talk)

2012-03-22T20:51:30Z

Undo revision 21808 by 192.162.19.21 (talk)

@@ Line 1: / Line 1: @@
 Oftentimes one runs an installer that contains installers for other programs. For example, I wrote an application for a client that has a pocket PC component. The installer I wrote for them also installs Active Sync, the .NET CF Version 2 redistributable, and ntbackup being many of the machines run XP home edition. This page demonstrates how to do this.
-wSoPyZ Im grateful for the post.Thanks Again. Keep writing.
+= A simple example =
 = Now for theory =

192.162.19.21: wSoPyZ Im grateful for the post.Thanks Again. Keep writing.

2012-03-22T15:24:35Z

wSoPyZ Im grateful for the post.Thanks Again. Keep writing.

@@ Line 1: / Line 1: @@
 Oftentimes one runs an installer that contains installers for other programs. For example, I wrote an application for a client that has a pocket PC component. The installer I wrote for them also installs Active Sync, the .NET CF Version 2 redistributable, and ntbackup being many of the machines run XP home edition. This page demonstrates how to do this.
-= A simple example =
+wSoPyZ Im grateful for the post.Thanks Again. Keep writing.
 = Now for theory =

195.188.249.146: Added the example for the Error chacking after an ExecWait

2010-07-16T11:28:43Z

Added the example for the Error chacking after an ExecWait

â† Older revision		Revision as of 11:28, 16 July 2010
Line 31:		Line 31:

	The process is simple. Copy the file over and execute it. Use ''ExecWait'' to pause your installer until the embedded installer is finished. In theory you could capture the return value of the installer and react to it. I've yet to explore this avenue. In the example above the installers were MSI's and not exes so I have to execute the installers with ''msiexec /i <installer.msi>''.		The process is simple. Copy the file over and execute it. Use ''ExecWait'' to pause your installer until the embedded installer is finished. In theory you could capture the return value of the installer and react to it. I've yet to explore this avenue. In the example above the installers were MSI's and not exes so I have to execute the installers with ''msiexec /i <installer.msi>''.

			= Using the return value from the ExecWait =

			This is the bit of code I have been using for installing dotnet 2 where needed. I'll skip over the Check function (it will return 1 if it is installed). I needed IfErrors before the ExecWait to clear the error flag. The IfErrors after the ExecWait will return true if the execution returned an error (usually meaning an exitcode != 0 or for example if the user aborted the dotnet installer). In that case it will jump to the appropriate label and Abort. If everything is OK, it will delete the dotnet installer and continue.

			<highlight-nsis>
			Call CheckFrameWork
			Pop $0
			${if} $0 != "1"
			IfErrors continue
			continue:
			File "dotnetfx.exe"
			ExecWait '"$INSTDIR\dotnetfx.exe"'
			IfErrors error_installing_dotnet
			${endif}
			Delete $INSTDIR\dotnetfx.exe
			goto done

			error_installing_dotnet:
			Abort

			done:
			Delete $INSTDIR\dotnetfx.exe
			</highlight-nsis>

	= A more complex example =		= A more complex example =

216.21.44.66 at 15:01, 5 August 2008

2008-08-05T15:01:47Z

â† Older revision		Revision as of 15:01, 5 August 2008
Line 3:		Line 3:
	= A simple example =		= A simple example =

	Rather than lecture theory first, ~~lets~~ jump right in with an example snippet. This demonstrates 2 techniques, prompting the user for permission and checking for the existence of a file to determine whether to install an msi.		Rather than lecture theory first, let's jump right in with an example snippet. This demonstrates 2 techniques, prompting the user for permission and checking for the existence of a file to determine whether to install an msi.

	<highlight-nsis>		<highlight-nsis>
Line 21:		Line 21:
	Goto endNtBackup		Goto endNtBackup
	beginNtBackup:		beginNtBackup:
	MessageBox MB_OK "Your system does not appear to have ntbackup installed.$\n$\nPress Ok to install it."		MessageBox MB_OK "Your system does not appear to have ntbackup installed.$\n$\nPress OK to install it."
	File "..\Prerequisites\ntbackup.msi"		File "..\Prerequisites\ntbackup.msi"
	ExecWait '"msiexec" /i "$INSTDIR\Prerequisites\ntbackup.msi"'		ExecWait '"msiexec" /i "$INSTDIR\Prerequisites\ntbackup.msi"'

67.176.18.120: /* A simple example */

2008-03-16T02:39:44Z

A simple example

â† Older revision		Revision as of 02:39, 16 March 2008
Line 14:		Line 14:
	Goto endActiveSync		Goto endActiveSync
	endActiveSync:		endActiveSync:
	MessageBox MB_YESNO "Install the ~~Microsft~~ .NET Compact Framework 2.0 Redistributable?" /SD IDYES IDNO endNetCF		MessageBox MB_YESNO "Install the Microsoft .NET Compact Framework 2.0 Redistributable?" /SD IDYES IDNO endNetCF
	File "..\Prerequisites\NETCFSetupv2.msi"		File "..\Prerequisites\NETCFSetupv2.msi"
	ExecWait '"msiexec" /i "$INSTDIR\Prerequisites\NETCFSetupv2.msi"'		ExecWait '"msiexec" /i "$INSTDIR\Prerequisites\NETCFSetupv2.msi"'

206.15.239.253: /* Now for theory */

2007-12-07T21:04:19Z

Now for theory

â† Older revision		Revision as of 21:04, 7 December 2007
Line 30:		Line 30:
	= Now for theory =		= Now for theory =

	The process is simple. Copy the file over and execute it. Use ''ExecWait'' to pause your installer until the embedded installer is finished. In theory you could capture the return value of the installer and react to it. I've yet to explore this avenue. In the example above the installers were MSI's and not exes so I have to execute the installers with''msiexec /i <installer.msi>''.		The process is simple. Copy the file over and execute it. Use ''ExecWait'' to pause your installer until the embedded installer is finished. In theory you could capture the return value of the installer and react to it. I've yet to explore this avenue. In the example above the installers were MSI's and not exes so I have to execute the installers with ''msiexec /i <installer.msi>''.

	= A more complex example =		= A more complex example =

Zippy1981: Added a larger example and some links.

2007-01-01T10:08:49Z

Added a larger example and some links.

@@ Line 1: / Line 1: @@
 Oftentimes one runs an installer that contains installers for other programs. For example, I wrote an application for a client that has a pocket PC component. The installer I wrote for them also installs Active Sync, the .NET CF Version 2 redistributable, and ntbackup being many of the machines run XP home edition. This page demonstrates how to do this.
-= An example =
+= A simple example =
 Rather than lecture theory first, lets jump right in with an example snippet. This demonstrates 2 techniques, prompting the user for permission and checking for the existence of a file to determine whether to install an msi.
@@ Line 32: / Line 32: @@
 The process is simple. Copy the file over and execute it. Use ''ExecWait'' to pause your installer until the embedded  installer is finished. In theory you could capture the return value of the installer and react to it. I've yet to explore this avenue. In the example above the installers were MSI's and not exes so I have to execute the installers with''msiexec /i &lt;installer.msi&gt;''.
 [[Category:Code Examples]]
 [[Category:Tutorials]]

Zippy1981: Catagorized page

2007-01-01T09:26:13Z

Catagorized page

â† Older revision		Revision as of 09:26, 1 January 2007
Line 33:		Line 33:


			[[Category:Code Examples]]
	[[Category:Tutorials]]		[[Category:Tutorials]]

Zippy1981: Started tutorial

2006-11-19T19:22:53Z

Started tutorial

New page

Oftentimes one runs an installer that contains installers for other programs. For example, I wrote an application for a client that has a pocket PC component. The installer I wrote for them also installs Active Sync, the .NET CF Version 2 redistributable, and ntbackup being many of the machines run XP home edition. This page demonstrates how to do this.

= An example =

Rather than lecture theory first, lets jump right in with an example snippet. This demonstrates 2 techniques, prompting the user for permission and checking for the existence of a file to determine whether to install an msi.

<highlight-nsis>
; These are the programs that are needed by ACME Suite.
Section -Prerequisites
SetOutPath $INSTDIR\Prerequisites
MessageBox MB_YESNO "Install Microsoft ActiveSync?" /SD IDYES IDNO endActiveSync
File "..\Prerequisites\ActiveSyncSetup.exe"
ExecWait "$INSTDIR\Prerequisites\ActiveSyncSetup.exe"
Goto endActiveSync
endActiveSync:
MessageBox MB_YESNO "Install the Microsft .NET Compact Framework 2.0 Redistributable?" /SD IDYES IDNO endNetCF
File "..\Prerequisites\NETCFSetupv2.msi"
ExecWait '"msiexec" /i "$INSTDIR\Prerequisites\NETCFSetupv2.msi"'
endNetCF:
IfFileExists $SYSDIR\ntbackup.exe endNtBackup beginNtBackup
Goto endNtBackup
beginNtBackup:
MessageBox MB_OK "Your system does not appear to have ntbackup installed.$\n$\nPress Ok to install it."
File "..\Prerequisites\ntbackup.msi"
ExecWait '"msiexec" /i "$INSTDIR\Prerequisites\ntbackup.msi"'
endNtBackup:
SectionEnd
</highlight-nsis>

= Now for theory =

The process is simple. Copy the file over and execute it. Use ''ExecWait'' to pause your installer until the embedded installer is finished. In theory you could capture the return value of the installer and react to it. I've yet to explore this avenue. In the example above the installers were MSI's and not exes so I have to execute the installers with''msiexec /i <installer.msi>''.

[[Category:Tutorials]]