I'm not sure what you require by way of an example. In my observations...
- Make an MSI package of several features/components. - Make a bootstrapper for your MSI with "setup" in the name. - Install the package. - Run the setup on Vista, select Repair and save the log file (automatically created in %TMP%). - Run the msi this time, select Repair again and save the log file also. Now, the two events will be obviously different because the first will trigger a UAC prompt as soon as it runs because of the special nature of exe files called "setup". The second will not have a UAC prompt... ever. So what differences will you see in the log? In my experience, a hell of a lot, but of concern are the properties being passed the the Server side - here are some examples. ---RUNNING BOOTSTRAPPER--- MSI (s) (24:94) [18:19:28:261]: PROPERTY CHANGE: Adding ROOTDRIVE property. Its value is 'C:\'. MSI (s) (24:94) [18:19:28:261]: PROPERTY CHANGE: Adding INSTALLLEVEL property. Its value is '1'. ---RUNNING MSI DIRECTLY--- MSI (s) (24:14) [18:18:39:150]: Ignoring disallowed property ROOTDRIVE MSI (s) (24:14) [18:18:39:150]: PROPERTY CHANGE: Adding INSTALLLEVEL property. Its value is '1'. What if the value of ROOTDRIVE is important for subsequent CAs? These lines 'ignoring disallowed property' exist when attempting to pass the location of every single component in my package. I hope this is the sort of thing you were after, Gareth -- View this message in context: http://www.nabble.com/Shield-Decoration-on-buttons-tf3566512.html#a10622403 Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
