Sunday, January 11, 2004, 2:13:49 PM, you wrote: > Can you please elaborate? I don't quite understand the relationship > between the UI sequence and the execute sequence: You're not alone!<g> At work, we have a wall where we post clippings about MSI weirdnesses; we call it the "MSI Hall of Misery" because it usually represents days of research and experimenting without much to show for the effort... > - Is it true that, with full UI, it first executes the entire UI > sequence, and then the full execute sequence? Then why do people > typically duplicate actions in both sequences? Yes. The UI sequence goes through the "ready to install" dialog and then the execute sequence takes over. That's where stuff actually gets installed. The UI sequence then picks back up for the "install complete" dialog. You need to duplicate many actions so that the UI accurately reflects what the actions do (usually setting properties like directory names). They have to exist in the execute sequence if they affect how the system is modified and also if you want a silent install to work. Interesting sidenote: Both Office (2000 and later) and Visual Studio (2002 and later) use MSI but only for the execute sequence. The UIs were coded in C/C++. > I'm somewhat worried that the action would be executed even after > the user was already queried for the targetdir (although the > condition should avoid TARGETDIR being reset). Yes, you want to keep the same condition in both sequences. That lets a user pass in a default installation directory for both full-UI and silent installs. > Also, I currently install by default into [WindowsVolume]PythonXY. > Would it be better to install into [ROOTDIR]PythonXY, as this would > be the drive with most space? I assume you mean ROOTDRIVE and I'd definitely agree that's the right default directory. If anyone still uses a network install of Windows, WindowsVolume would be on the network. -- sig://boB http://foobob.com
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4