I figured that is where the funny msi name came from, but it seems backwards to display the cached msi file name in place of the signed installation file name, but show the original "real" file name for an unsigned installation file.
BTW, I assume you are the Phil Wilson who is the author of "The Definitive Guide to Windows Installer" that is sitting on my desk. Have you considered updating the book to use Wix instead of Visual Studio? That would be really great. It seems like a good portion of the book is spent talking about what the Visual Studio generated installers can't do and how to get around it. Jeff Bean Wilson, Phil wrote: > > This might be just MSI behavior, which is to create that random MSI file > name in the temp folder and use that for the install. If you monitor the > temp folder I suspect you'd see that random MSI file name there, and I > believe it's what gets copied to the cached location in > Windows\installer. > > Phil Wilson > -- View this message in context: http://www.nabble.com/UAC-elevation-prompt-for-signed-MSI-file-under-Vista-tf3079382.html#a8569435 Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
