Lines Matching full:msi

4 For testing, the installer should be built with the Tools/msi/build.bat
10 Tools/msi/buildrelease.bat script and environment variables:
42 CAB and MSI files and a single EXE.
48 Each MSI contains the logic required to install a component or feature
53 embedded into their associated MSI and are never seen by users.
57 associated MSI is not downloaded. This allows the installer to offer
65 Tools\msi\get_externals.bat. (Note that this is in addition to the
76 For testing, the installer should be built with the Tools/msi/build.bat
101 Tools/msi/buildrelease.bat script:
226 Packages appear as subdirectories of Tools/msi (other than the bundle/
228 single MSI. Packages are built with the WiX Toolset. Some project files
249 example, and msi.targets and csv_to_wxs.py for the implementation. This
253 All packages are built with the Tools/msi/common.wxs file, and so any
277 project to perform {{substitutions}} as defined in msi.targets. They
285 will represent the Python installer. It is built from Tools/msi/bundle
286 with packages references in Tools/msi/bundle/packagegroups.
312 MSI packages are installed or uninstalled based on their current state
353 (Default installation locations are set in Tools\msi\bundle\bundle.wxs.)