The next edition will use Wix - should be getting started soon. Having said that, it's the fact that Visual Studio has flaws and limitations that made it a useful place to start. There's scope to dissect the setups, explain how they work, then add missing functionality with Orca and automation, and use it contrast the ServiceInstall table instead of Installer classes etc. When Wix does everything you need with an MSI file, what interesting extensions can you show using Orca? Can it be made more interesting than just "this is the Wix, these are the MSI tables". That's the general challenge. People generally label it as a Visual Studio book, which means I didn't get that idea across. Is it easier to learn car repair by restoring a broken vehicle? Or do I open the Lexus hood and just point at everything, saying what it does? If the examples are Wix will people say oh, it's a Wix book and discard it because they want a Windows Installer book? I suspect that the disconnect between the technology (MSI) and the tool is greater with setups than in many other areas, especially with Visual Studio and InstallShield (less so in Wix) and that's the difficulty. It's like writing a book about the .NET framework - examples in IL would make people crazy, but if if you use C# do the VB people throw it away with "oh, it's a C# book"? All those questions......
Phil Wilson -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Bean Sent: Wednesday, January 24, 2007 10:22 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] UAC elevation prompt for signed MSI file under Vista 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-Vis ta-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=DEVDE V _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- 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
