home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Chip 2001 June
/
Chip_2001-06_cd1.bin
/
zkuste
/
vbasic
/
Data
/
Utility
/
MSISDK15.msi
/
ReadMe.txt
< prev
next >
Wrap
Text File
|
2000-11-14
|
11KB
|
189 lines
Windows Installer 1.5 SDK Release - Microsoft Corporation
---------------------------------------------------------------------------
This release includes the following components, in the indicated folders:
ReadMe.txt - this file, contents and notes
License.rtf - SDK license agreement
Redist.txt - redistibution terms and conditions
Redist - components that may be redistributed with your application
WINNT\InstMsi.exe - Windows Installer self-installer for use with Windows NT4 and Windows 2000
WIN9x\InstMsi.exe - Windows Installer self-installer for use with Windows 95, Windows 98, Windows ME
Help
Msi.chm+Msi.chi - Documentation for Windows Installer, HTML help format (see note below)
Include
Msi.h - install management API functions
MsiQuery.h - database and custom action API functions
MsiDefs.h - property names and database data bit flags
MergeMod.h - definitions for use with MergeMod.dll COM object
PatchApi.h - definitions for use with MsPatchC.lib and MsPatchC.dll
PatchWiz.h - definitions for use with the installer patch package creation tool
Lib
Msi.lib - import lib for MSI API functions
MsPatchC.lib - import lib for patch generation engine MsPatchC.dll
PatchWiz.lib - import lib for patch package creation tool PatchWiz.dll
Tools
Instlr11.adm - used with the Group Policy Editor. See the "System Policy" help topic.
Instlr1.adm - used with the Group Policy Editor and Windows Installer version 1.0
Orca.msi - graphical table editor supporting validation and merge modules
MsiVal2.msi - command-line installer package validation tool, provides darice.cub and logo.cub files
MsiDb.exe - database import, export, merge, transform
MsiMig.dll - Custom Action for migration of 1.0 cached packages to 1.1 of the Windows Installer
MsiMig.exe - Command line utility for administrators migrating 1.0 cached packages to 1.1
MsiMsp.exe - patch package creation
MsiInfo.exe - summary information property manager, string pool validation
MsiMerg.exe - merges two databases
MsiTran.exe - generates and applies database transforms
MsiZap.exe - used to remove selected MSI management data from a machine. Use with caution.
MsiCert.exe - used to populate the MsiDigitalSignature and MsiDigitalCertificate tables
MsiFiler.exe - used to populate file versions, sizes, and languages
MsiTool.mak - shared makefile for tools and custom actions
MergeMod.dll - COM object providing support for installer merge modules
Tools\110
darice.cub - Windows Installer version 1.1 complete validation suite
mergemod.cub - Windows Installer version 1.1 merge module validation suite
logo.cub - Windows Installer version 1.1 logo validation suite
Tools\120
darice.cub - Windows Installer version 1.2 complete validation suite
mergemod.cub - Windows Installer version 1.2 merge module validation suite
logo.cub - Windows Installer version 1.2 logo validation suite
Web
msistuff.exe - used to populate resources in setup.exe. Only works on Windows NT.
setup.exe - internet download executable for creating installs from the web
Patching
MakeCab.exe - general compressed file cabinet generation tool, not installer-specific
MPatch.exe - test application to create a patch file using MsPatchC.dll
APatch.exe - test application to apply a patch using MsPatchA.dll (part of InstMsi package)
MsPatchC.dll - patch file creation engine, used by PatchWiz.dll and MPatch.exe
PatchWiz.dll - installer patch package creation tool (documented in Msi.chm)
Template.pcp - schema for patch wizard project settings
Example.pcp - sample project settings for patch wizard
Database
Schema.msi - database containing all standard tables, but no installation data
Schema.msm - merge module containing all standard module tables, but no installation data
Sequence.msi - recommended sequence table actions
UISample.msi - sample database demonstrating a UI implementation
Error.mst - transform to provide debug error messages during development
Intl - localized Error and ActionText tables in multiple languages
Database\100
Schema.msi - Windows Installer version 1.0 database containing all standard tables
Sequence.msi - Windows Installer version 1.0 recommended sequence table actions
Database\110
Schema.msi - Windows Installer version 1.1 database containing all standard tables
Sequence.msi - Windows Installer version 1.1 recommended sequence table actions
Schema.msm - Windows Installer version 1.1 merge module containing all standard module tables
Database\120
Schema.msi - Windows Installer version 1.2 database containing all standard tables
Sequence.msi - Windows Installer version 1.2 recommended sequence table actions
Schema.msm - Windows Installer version 1.2 merge module containing all standard module tables
Samples - examples demonstrating the use of the Windows Installer APIs
Create.cpp - sample DLL custom action for creating user accounts on the local machine
CustAct1.cpp - sample DLL custom action for testing
CustExe1.cpp - sample EXE custom action for testing
MsiLoc.cpp - sample resource file generation and import tool (export an msi for use with localization of .RES files)
MsiLoc.txt - readme for msiloc.cpp and usage of the corresponding compiled exe
MsiMerg.cpp - sample database merge tool
MsiTran.cpp - sample transform creation and application tool
Process.cpp - sample DLL custom actions (ProcessUserAccounts, UninstallUserAccounts) for user account creation and deletion
Remove.cpp - sample DLL custom action for removing user accounts from the local machine
Scripts - folder containing doc and scripts to perform a variety of installer-related tasks
Tutorial.cpp - sample DLL custom action for invoking an installed file at the end of setup
---------------------------------------------------------------------------
Windows Installer core files installed by installation package InstMsi.exe:
Msi.dll - installation engine, use by install clients and install service
MsiExec.exe - command-line invocation of install functions, and service control functions
MsiHnd.dll - UI process, loaded only when full UI is authored and used for installation
Other files that are updated as needed by installation package InstMsi.exe:
riched20.dll, usp10.dll, msls31.dll - rich-edit and complex script support
cabinet.dll - extraction of files from compressed file cabinets
imagehlp.dll - used for import table binding
mspatcha.dll - used to apply file-level patches
shfolder.dll - special shell folder location and creation
---------------------------------------------------------------------------
Notes:
Msi.chm is the primary source of information about the Windows Installer, and contains both an
introduction to the new model, as well as detailed reference material for developers.
See the topic "Windows Installer Examples" to get started with simple packages.
If HTML help is already installed on your system, msi.chm can be invoked via file association
HTML help can be installed from: http://msdn.microsoft.com/workshop/author/htmlhelp/localize.asp
The .msi packages in the SDK may be installed by activating them in the Windows Explorer,
or by using "MsiExec.exe -i path_to_package". Use "MsiExec.exe -?" to see more options.
The object model is exposed as the ProdId: WindowsInstaller.Installer
UISample.msi provides a sample UI sequence, but that sequence will not function
properly until the database has been populated with valid installation data.
For help in populating a database with valid installation data, see the help topic
titled "An Installation Example" under "Windows Installer Examples". For an
example of a completed installation package that uses the same UI sequence as
UISample.msi, install one of the msi packages under the Tools or SampProd folders.
Set the ShowUserRegistrationDlg property in the Property table to 0 if you do not
wish to have the UserRegistrationDlg appear.
UISample.msi together with Sequence.msi and schema.msi will provide a framework which can
then be populated with valid installation data. Use the MsiMerg tool, MsiDb tool or the
WiMerge.vbs script to merge the databases together (merging two at a time).
The custom action samples process.cpp, remove.cpp, create.cpp, and tutorial.cpp are the source
files for the sample custom actions described in the msi.chm file. See the msi.chm file for
more information regarding their usage.
---------------------------------------------------------------------------
Compiling sample code:
There are two options for compiling the sample code in the Samples subfolder:
use nmake or use a project in the MSDev environment.
To use nmake, make certain that the MSVCDIR environment variable is set. You can
generally run the VCVARS32.BAT to set this. VCVARS32.BAT is located in the BIN
subdirectory of your VC install. The command line to compile the CUSTACT1.CPP
sample file (given default install locations for both Microsoft Visual C++ 6
and the Windows Installer SDK) would look like this:
C:\program files\MsiIntel.SDK\Samples> nmake -f custact1.cpp include="%include%;c:\program files\MsiIntel.SDK\Include" lib="%lib%;c:\program files\MsiIntel.SDK\Lib"
Note: the quotes are included because the default install locations include spaces in path names.
If the INCLUDE and LIB environment variables on the machine and the SDK install location
do not have spaces in the path, then the quotes are unnecessary.
To use the MSDev environment, create a new Win32 EXE or Win32 DLL project, and
add the appropriate file as a source. MSI.LIB will need to added to the library
list in the Project Settings dialog. MsiIntel.SDK\Include and MsiIntel.SDK\Lib
directories will need to be added to the Directories tab under Tools\Options.
All SDK source files contain comments on how to compile the sample code. See the
source file for more specific build information.
Note that initmsi.cpp does not compile.
---------------------------------------------------------------------------
Known issues:
Msi.chm is not yet properly integrated w/ the typelib in msi.dll - context sensitive
help is not available in VB w/ this release.
Tools that create customization transforms require special considerations that are
not yet documented in msi.chm. A KB article on this topic will be published
shortly after this SDK is released - go to http://support.microsoft.com/support/search/c.asp
and enter "Q225522" in the "My Question Is" box.
Additional support articles and solutions will be placed on
http://support.microsoft.com/support/search/c.asp as they become available.