Menu
▾
▴
[WiX-commits] wix/src/chm/html wixfailwhendeferred.htm, NONE, 1.1 WixUI_customizations.htm, 1.1, 1.2 WixUI_dialog_library.htm, 1.7, 1.8 codepage.htm, 1.2, 1.3 shellexec.htm, 1.2, 1.3 using_standard_customactions.htm, 1.2, 1.3
Update of /cvsroot/wix/wix/src/chm/html In directory sc8-pr-cvs9.sourceforge.net:/tmp/cvs-serv12321/src/chm/html Modified Files: WixUI_customizations.htm WixUI_dialog_library.htm codepage.htm shellexec.htm using_standard_customactions.htm Added Files: wixfailwhendeferred.htm Log Message: WixBuild: Version 3.0.4220.0 MiCarls: Also allow heat to harvest embedded typelibs as non-admin on Vista BobArnso: Change FileVersionFromString to allow "partial" versions (e.g., 1.2 instead of 1.2.3.4). CAraman: Fixes for compiling at /W4 /WX, and annotations for static analysis. AaronSte: SFBUG:1986923 - do not display modal dialogs at the top of the screen in WixUI. SFBUG:2000147 - provide additional Install/Repair/Uninstall control in WixUI to prevent displaying ElevationShield in per-user MSIs. NeilE: Added two new how-to topics to the documentation, one for installing .NET Framework via a bootstrapper, and a second on launching the installed application after setup is complete. AaronSte: Adding more detail to the File element documentation in wix.xsd. Fixing several broken links in wix.xsd. RobMen: SFBUG:1897640 - give the WixVariableResolver a localizer to handle cases where Outputs are being saved with loc variables in file paths. AaronSte: Adding a topic to wix.chm for WixFailWhenDeferred custom action. a-broge: SFBUG:1967749 - Fix light.exe validation failing builds on Vista systems. MiCarls: Fix a number of FXCop issues in various parts of the toolset. BobArnso: - Fixed calling convention of Wow64 functions in xmlutil. - Added XmlReportParseError to provide details about parse errors. Index: WixUI_customizations.htm =================================================================== RCS file: /cvsroot/wix/wix/src/chm/html/WixUI_customizations.htm,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 *** WixUI_customizations.htm 30 May 2008 07:23:09 -0000 1.1 --- WixUI_customizations.htm 27 Jun 2008 07:03:22 -0000 1.2 *************** *** 33,37 **** <li>Use a dialog set other than the WixUI_Minimal set. This problem typically only occurs when the license agreement screen is the first one displayed during setup, which only happens with the WixUI_Minimal dialog set.</li> </ul> - </p> <h2>Replacing the default bitmaps</h2> <p>The WixUI dialog library includes default bitmaps for the background of the --- 33,36 ---- *************** *** 105,108 **** --- 104,111 ---- setup project. As long as you continue using the WixUIExtension, your custom fragments will be able to find the built-in dialog fragments.</p> + <h2>Adding a checkbox to the final UI page</h2> + <p>The final page used in the standard dialog sets supports an optional + checkbox. For an example of using this checkbox see + <a href="run_program_after_install.htm">How To: Run the Installed Application After Setup</a>.</p> </body> </html> --- NEW FILE: wixfailwhendeferred.htm --- (This appears to be a binary file; contents omitted.) Index: codepage.htm =================================================================== RCS file: /cvsroot/wix/wix/src/chm/html/codepage.htm,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -d -r1.2 -r1.3 *** codepage.htm 18 Jun 2008 08:59:56 -0000 1.2 --- codepage.htm 27 Jun 2008 07:03:22 -0000 1.3 *************** *** 14,18 **** <p>To support authoring a single package that can be localized into multiple languages, you can set the <a href="wix_xsd_Package.htm">Package</a>/@SummaryCodepage or <a href="wix_xsd_PatchInformation.htm">PatchInformation</a>/@SummaryCodepage element to an localization expression like !(loc.SummaryCodepage). You then define the SummaryCodepage value in a <a href="wxl.htm">localization file</a>, typically ending in a .wxl extension. The root WixLocalization element also supports a Codepage attribute that is used to encode the rest of the package database.</p> <p>You can also set the code page to 0. In this case, Windows Installer treats strings as neutral, meaning that you can only safely use ASCII characters - the first 128 ANSI characters - but the database will be supported across Windows platforms. See <a href="http://msdn2.microsoft.com/library/aa368057.aspx" target="_blank">Creating a Database with a Neutral Code Page</a> for more information.</p> ! <p>For a walkthrough about how to author a build localized packages using WiX, read <a href="http://blogs.msdn.com/robmen/archive/2004/11/30/272141.aspx" target="_blank">Creating localized MSI files using WiX toolset and .wxl files</a>.</p> </body> </html> --- 14,21 ---- <p>To support authoring a single package that can be localized into multiple languages, you can set the <a href="wix_xsd_Package.htm">Package</a>/@SummaryCodepage or <a href="wix_xsd_PatchInformation.htm">PatchInformation</a>/@SummaryCodepage element to an localization expression like !(loc.SummaryCodepage). You then define the SummaryCodepage value in a <a href="wxl.htm">localization file</a>, typically ending in a .wxl extension. The root WixLocalization element also supports a Codepage attribute that is used to encode the rest of the package database.</p> <p>You can also set the code page to 0. In this case, Windows Installer treats strings as neutral, meaning that you can only safely use ASCII characters - the first 128 ANSI characters - but the database will be supported across Windows platforms. See <a href="http://msdn2.microsoft.com/library/aa368057.aspx" target="_blank">Creating a Database with a Neutral Code Page</a> for more information.</p> ! <p>For a walkthrough about how to author a build localized packages using WiX ! see <a href="make_installer_localizable.htm">How To: Make your installer ! localizable</a> and <a href="build_a_localized_version.htm">How To: Build a ! localized version of your installer</a>.</p> </body> </html> Index: shellexec.htm =================================================================== RCS file: /cvsroot/wix/wix/src/chm/html/shellexec.htm,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -d -r1.2 -r1.3 *** shellexec.htm 21 Sep 2007 07:58:33 -0000 1.2 --- shellexec.htm 27 Jun 2008 07:03:22 -0000 1.3 *************** *** 16,37 **** <p> ! Here's how you could use WixShellExecute to launch a readme file based on its File/@Id attribute value using WixUI's support for adding a checkbox to the final dialog: ! </p> ! ! <pre> ! <CustomAction Id="LaunchReadme" BinaryKey="WixCA" DllEntry="WixShellExec" Execute="immediate" Return="check" Impersonate="yes" /> ! <Property Id="WIXUI_EXITDIALOGOPTIONALCHECKBOXTEXT" Value="Open readme" /> ! <Property Id="WixShellExecTarget" Value="[#readme]" /> ! <UI> ! <UIRef Id="WixUI_Minimal" /> ! <Publish Dialog="ExitDialog" Control="Finish" Event="DoAction" Value="LaunchReadme" Order="1">WIXUI_EXITDIALOGOPTIONALCHECKBOX = 1 and NOT Installed</Publish> ! </UI> ! </pre> ! ! <p> ! If you want to run more than one command line in the immediate sequence then you need to schedule WixShellExecute ! multiple times and set the WixShellExecuteTarget property (using a type 51 custom action) right before you want ! each of them executed. ! </p> </body> --- 16,23 ---- <p> ! For a step-by-step example of how to use the ShellExecute custom action to ! launch a program at the end of install see the ! <a href="run_program_after_install.htm">How To: Run the Installed Application After Setup</a> ! topic.</p> </body> Index: WixUI_dialog_library.htm =================================================================== RCS file: /cvsroot/wix/wix/src/chm/html/WixUI_dialog_library.htm,v retrieving revision 1.7 retrieving revision 1.8 diff -C2 -d -r1.7 -r1.8 *** WixUI_dialog_library.htm 30 May 2008 07:23:09 -0000 1.7 --- WixUI_dialog_library.htm 27 Jun 2008 07:03:22 -0000 1.8 *************** *** 22,30 **** difference between typical and complete installs.</p> <p><i>Note</i>: WixUI_Mondo uses ! <a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/setinstalllevel_controlevent.asp" target="_blank"> SetInstallLevel</a> control events to set the install level when the user chooses Typical or Complete. For Typical, the install level is set to 3; for Complete, 1000. For details about feature levels and install levels, see ! <a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/installlevel.asp" target="_blank"> INSTALLLEVEL Property</a>.</p> --- 22,30 ---- difference between typical and complete installs.</p> <p><i>Note</i>: WixUI_Mondo uses ! <a href="http://msdn.microsoft.com/library/aa371688.aspx" target="_blank"> SetInstallLevel</a> control events to set the install level when the user chooses Typical or Complete. For Typical, the install level is set to 3; for Complete, 1000. For details about feature levels and install levels, see ! <a href="http://msdn.microsoft.com/library/aa369536.aspx" target="_blank"> INSTALLLEVEL Property</a>.</p> Index: using_standard_customactions.htm =================================================================== RCS file: /cvsroot/wix/wix/src/chm/html/using_standard_customactions.htm,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -d -r1.2 -r1.3 *** using_standard_customactions.htm 30 May 2008 07:23:10 -0000 1.2 --- using_standard_customactions.htm 27 Jun 2008 07:03:22 -0000 1.3 *************** *** 2,9 **** <head> <link rel=stylesheet type=text/css href=style.css> ! <title>Using Standard Custom Actions</title> </head> <body> ! <h1>Using Standard Custom Actions</h1> <p> --- 2,9 ---- <head> <link rel=stylesheet type=text/css href=style.css> ! <title>Adding Standard Custom Actions</title> </head> <body> ! <h1>Adding Standard Custom Actions</h1> <p> |