Hi, I've been thinking of trying this, but I have one question before I do. How does uninstall work? I presume you need to handle this in your Windows Forms program?
Nick -----Original Message----- From: Wilson, Phil [mailto:phil.wil...@wonderware.com] Sent: Wednesday, August 12, 2009 9:46 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] External Installer App with UI quietly controlling MSIinstallation There are plenty of .NET libraries out there. The "worst" ones use MSI.DLL as a COM reference and it's often unreliable because those interfaces are basically intended for late-binding using the installer's scripting model. The best ones (like Richard's) are just C# source code with P/Invoke to the Msi** Win32 API calls. The Win32 API has all you need, it's a just a matter of getting the P/Invoke calls right. The approach I've worked on is to use Windows .NET forms to wrap one or MSI (silent) installs and make it look like one product in Add/Remove Programs. The entire thing is driven with an Xml file that lists the forms you want to show, the MSI files to install, and the feature tree you want to see with some info about which MSI file the feature is in. The point is to be able to manage a collection of MSIs as if it's one product. Somewhere in MSDN there's a C++ example showing use of MsiSetExternalUIRecord to do an install and collect records to show in your UI, also an example with MsiSetExternalUI. Phil Wilson ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
