My apologies, my finger was faster on the "Send" button than my eyes were at noticing I forgot to change the subject line.
Julie -----Original Message----- From: Julie Campbell [mailto:[EMAIL PROTECTED] Sent: Monday, April 09, 2007 4:07 PM To: 'wix-users@lists.sourceforge.net' Subject: RE: WiX-users Digest, Vol 11, Issue 46 I don't know anything about PIA's, but if you have a .msi that you need to add to a bootstrapper, you want to create a directory in your VS-SDK directory as you mentioned. What goes in this directory is sometimes called "Bootstrapper Manifests", sometimes called "Bootstrapper Package". The directory structure should be something like (where SDK:\ = C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\BootStrapper\) SDK:\Packages\MyPackage\product.xml SDK:\Packages\MyPackage\MyPackage.msi SDK:\Packages\MyPackage\en\package.xml The product.xml is going to look something like this one I created for IVI Shared Components: <?xml version="1.0" encoding="utf-8" ?> <!-- Set appropriate ProductCode --> <Product xmlns="http://schemas.microsoft.com/developer/2004/01/bootstrapper"; ProductCode="Ivi.SharedComponents.1.4.0"> <!-- Reference your MSI package file --> <PackageFiles CopyAllPackageFiles="true"> <PackageFile Name="IviSharedComponents1.4.0.msi"/> </PackageFiles> <!-- Skip installation if MSI is installed on the system --> <InstallChecks> <MsiProductCheck Property="IsMSIInstalled" Product="{99A125D2-366A-49BE-A144-B6CFB9668A90}"/> </InstallChecks> <Commands Reboot="Defer"> <Command PackageFile="IviSharedComponents1.4.0.msi" Arguments=""> <InstallConditions> <BypassIf Property="IsMSIInstalled" Compare="ValueGreaterThan" Value="1"/> </InstallConditions> <ExitCodes> <!-- Standard Windows Installer return codes --> <ExitCode Value="0" Result="Success"/> <ExitCode Value="1641" Result="SuccessReboot"/> <ExitCode Value="3010" Result="SuccessReboot"/> <DefaultExitCode Result="Fail" FormatMessageFromSystem="false" String="GeneralFailure" /> </ExitCodes> </Command> </Commands> </Product> The package.xml is going to look something like this corresponding file: <?xml version="1.0" encoding="utf-8" ?> <Package xmlns="http://schemas.microsoft.com/developer/2004/01/bootstrapper"; Name="DisplayName" Culture="en"> <!-- TODO: Define strings --> <Strings> <String Name="DisplayName">IVI Shared Components 1.4.0</String> <String Name="Culture">en</String> <String Name="GeneralFailure">A fatal error occurred during the installation of [Your Package]</String> </Strings> </Package> Now, you have the "Bootstrapper Package" ready to be included in a bootstrapper. No compilation, registration, etc., required to get to this point. I do this "by hand", though the "Bootstrapper Manifest Generator" may get you to the same point (I don't like the tool, the GUI is all weird on my display). To include this in a bootstrapper, you are going to have a bootstrapper source file something like this, however you got there: <Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003";> <ItemGroup> <!-- Include the 'Product Code' for every package you want --> <BootstrapperFile Include="Microsoft.Net.Framework.2.0" /> <BootstrapperFile Include="Ivi.SharedComponents.1.4.0" /> </ItemGroup> <Target Name="Bootstrapper"> <GenerateBootstrapper BootstrapperItems="@(BootstrapperFile)" ComponentsLocation="Relative" CopyComponents="true" /> </Target> </Project> To build from the command line: Msbuild /val mybootstrapper.xml Hope this helps! Julie Campbell [EMAIL PROTECTED] (440) 498-3081 -----Original Message----- ------------------------------ Message: 3 Date: Mon, 9 Apr 2007 13:55:59 -0400 From: "Chris Bardon" <[EMAIL PROTECTED]> Subject: [WiX-users] Create MSBuild boostrap event to install Office PIAs To: <wix-users@lists.sourceforge.net> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="us-ascii" I was looking at the wiki article here (http://www.wixwiki.com/index.php?title=Deploying_Additional_Components) on bootstrapping, and I need to be able to extend the bootstrapper with my own component for the Office 2003 and 2007 PIAs. I checked out the tool from gotdotnet to generate the XML, but now I'm not sure what it's actually generating. Do I need to create my own directory and product XML file in the VS install directory (C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\BootStrapper\Packages\), or do I just need to have a manifest in the project directory that points to the file location? I'm assuming that for the office PIAs there's no "homesite" that I can set to have them auto download, and that I'll have to include the MSI with my redistributable, correct? Also, does anyone know if there's any danger in adding both the 2003 and 2007 PIAs as prerequisites if I want to support both versions? The assembly installers should only install what's appropriate, correct (I'm guessing that's why these are MSIs and not MSMs in the first place). Thanks, Chris _____________________________________________________________________________ Scanned by IBM Email Security Management Services powered by MessageLabs. For more information please visit http://www.ers.ibm.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
