A few more observations: People generally do what they already know how to do. For developers that means writing code. In the context of building setups, that's the difference between being a developer and being a setup developer. The latter would never write code for something that Windows (or WiX) gives you for free if you just learn how to do it. And yes, the remark about installs/uninstalls failing in the middle doesn't make sense when installs are transactional, roll back and so on. There's no such thing as "failing in the middle".
There is a comment that this WiX project was originally a Visual Studio setup project, and about difficulty with installing services. Visual Studio setup projects don't use the standard MSI ServiceInstall/ServiceControl tables - they use installer class code. If that installer class code was in fact the difficulty, it's ironic that using installer class code (instead of built-in functionality) was the problem with installing services that gave Windows Installer the bad rep, but now using code (instead of built-in functionality) *is* the preferred solution. So, as far as I can tell every single one of the problems mentioned in this thread (DTF custom actions, 32/64 bit, installing services) are ALL with custom action code and not Windows Installer. Phil Wilson -----Original Message----- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Friday, July 02, 2010 2:35 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Windows 7 Custom Action Registry problem He doesn't seem to care about using standard Windows Installer or even WiX functionality Rob. A direct quote: "our experience is that Windows Installer works if it is done perfectly and in the correct order. our code is defensive and deals with installs and uninstalls that failed in the middle. in addition we also deal with terminating the app. the original reason for the custom action is the difficulty we encountered when trying to deal with installing and uninstalling a service. despite much reading, much searching, and much experimentation Windows Installer would never work for us. so we created our own solution." All of which Windows Installer and/or WiX do perfectly well (rollback you say? What is this rollback?). Some people are always trying to ice skate uphill. Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the <Virtual Environment>** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -----Original Message----- From: Rob Mensching [mailto:r...@robmensching.com] Sent: 01 July 2010 22:57 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Windows 7 Custom Action Registry problem It seems so wrong to spend so much time trying to get a registry key when the Windows Installer will do it all for you plus handle rollback. On Thu, Jul 1, 2010 at 1:59 PM, Kurt Jensen <kurt.jen...@ophir-spiricon.com>wrote: > Thanks! > > I think the real problem is that the CA is being launched as a 32-bit > process (of course). now that I know the problem I have modified my > application code to first look in the "normal" part of the registry, > then look in Wow6432Node if the key is not found. that way it works > on a 32-bit OS, on a 64-bit OS when the CA runs as a 32-bit process, > and will continue to work if the CA some day starts running as a 64-bit process. > > thanks again for all the stimulation! > > -----Original Message----- > From: i...@roadrunner.com [mailto:i...@roadrunner.com] > Sent: Thursday, July 01, 2010 2:45 PM > To: General discussion for Windows Installer XML toolset. > Cc: Kurt Jensen > Subject: Re: [WiX-users] Windows 7 Custom Action Registry problem > > Here's one example how to do it with P/Invoke: > http://www.roelvanlisdonk.nl/?p=915 > > ---- Kurt Jensen <kurt.jen...@ophir-spiricon.com> wrote: > > That's it! > > > > So far I cannot find an equivalent in .NET but at least now I can > > track > down the communication breakdown... > > > > Thanks to all! > > > > > > -----Original Message----- > > From: i...@roadrunner.com [mailto:i...@roadrunner.com] > > Sent: Thursday, July 01, 2010 11:23 AM > > To: General discussion for Windows Installer XML toolset. > > Cc: Kurt Jensen > > Subject: Re: [WiX-users] Windows 7 Custom Action Registry problem > > > > > also, this solution was developed by another less install oriented > > > programmer for the original vsproj under VS2008. I moved the code > > > as-is over to WiX on a 32-bit install and it worked. now we are > > > adding a 64-bit install. if I change to having Windows Installer > > > do the job then I really am reinventing the wheel from our perspective. > > > > Maybe your keys get redirected? Check > HKLM\SOFTWARE\Wow6432Node\Spiricon\Version5. Maybe your values are there. > > If so, you need to add KEY_WOW64_64KEY to RegOpenKey (or whatever > > the > .NET equivalent is). > > > > ******************************************************************** > > ** This email and any files transmitted with it are confidential and > > intended solely for the use of the individual or entity to whom they > > are addressed. If you have received this email in error please > > notify the system manager. > > > > This footnote also confirms that this email message has been swept > > by MIMEsweeper for the presence of computer viruses. > > > > www.clearswift.com > > ************************************************************* > ------------------------------------------------------------------------ ------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at Portland House, Bressenden Place, London, SW1E 5BF (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77. You may contact Invensys plc on +44 (0)20 7821 3848 or e-mail inet.hqhelpd...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
