Soap Toolkit 3.

0 Redistributable Files
Microsoft Corporation.
July, 2002.

This document describes how to use SOAP Toolkit 3.0 redistributable modules.

Merge Modules

The following Microsoft Installer 2.0 merge modules are included in the redistributable
package:
• Soap3_core.msm
• Isapi3_files.msm
• Winhttp.msm

Soap3_core.msm and winhttp.msm are required for all soap installations and
isapi3_files.msm is dependent on soap3_core.msm.

Files

The following files are included:

Soap3_core.msm
File Destination Directory Register Platform
s
Mssoap30.dll \Program Files\Common Files\MSSoap\Binaries Yes ALL
WHSC30.dll \Program Files\Common Files\MSSoap\Binaries Yes NT4,
W2K, XP
WISC30.dll \Program Files\Common Files\MSSoap\Binaries Yes ALL
MSSOAPR3.dll c:\Program Files\Common No ALL
Files\MSSoap\Binaries\Resources\1033

Isapi3_files.msm
File Destination Directory Register Platform
s
SOAPIS30.dll \Program Files\Common Files\MSSoap\Binaries Yes ALL
SOAPVDIR.cmd \Program Files\MSSOAP\Binaries No ALL
_svdir.cmd \Program Files\MSSOAP\Binaries No ALL

Winhttp.msm
File Destination Directory Register Platforms
winhttp.dll \WINNT\system32 Yes NT4, W2K, XP

Requirements
SOAP Toolkit components require MSXML4 SP1 to be installed. You can obtain MSXML 4
SP1 merge modules on MSDN:
http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?
url=/msdn-files/027/001/766/msdncompositedoc.xml

SOAP Toolkit 3.0 Merge modules require using the latest version of Microsoft Windows®
Installer, which is part of Microsoft Windows XP. The Installer is released with many
newer Microsoft products, but may not be on your computer. You can download the
latest version of Microsoft Installer from these locations:
Windows Installer Redistributable for Windows 95 and Windows 98
Windows Installer Redistributable v 1.1 for Windows NT 4.0 (x86)

How to redistribute SOAP Toolkit 3.0 components

With addition of the winhttp.msm, merging the SOAP Toolkit 3.0 redistributable modules
became more complicated then it used to be for the previous 2.0 SP2 version.
The winhttp.msm contains installers for the system http library Winhttp 5.1
(winhttp.dll).
The reason for complexity is that winhttp.msm contains platform specific installers of the
for each W2K, NT4 and XP. Once installed, winhttp.dll file becomes System File
Protected. Microsoft does not provide any means to uninstall winhttp.dll.

Merging winhttp.msm requires additional properties set/updated in order for your

installer to work correctly:
1. Set Property ALLUSERS=1 in your installer msi project.
2. Ensure that the following 3 custom actions that come with winhttp.dll:
QFE_XP.6AB4B1E3_9BF2_4A9B_BC64_CE23E2B44659
QFE_2K.6AB4B1E3_9BF2_4A9B_BC64_CE23E2B44659
QFE_XP.6AB4B1E3_9BF2_4A9B_BC64_CE23E2B44659
have InstallExecuteSequence immediately after InstallInitialize and
RemoveExistingProducts actions, but before any component from the
soap_core.msm.
If these properties are not set correctly you may run into fatal failures when trying to
install and uninstall your product on NT4, W2K and XP platforms.

Microsoft provides two development tools to create Windows Installer msi packages. The
first one is Visual Studio.Net – Setup and Deployment Projects. The second one is
Orca.exe (Editor for Windows Installing packages and merge modules) that comes with
the Microsoft Platform SDK available for download at
http://www.microsoft.com/msdownload/platformsdk/sdkupdate/
After installation of the Platform SDK, launch the Platform SDK\Bin\Orca.msi to install
Orca.exe.
Using Visual Studio.Net you can easily create initial MSI project and add SOAP Toolkit
3.0 Merge Modules. But unfortunately it is not obvious to set/update properties as
mentioned in 1 and 2 above.
This is where the powerful Orca editor helps you.
1. Open with Orca your msi created in VS.Net
2. Find and select Property table in the left column. Search ALLUSERS property in
the property list appeared on the right pane. If it does not exist – add ALLUSERS
property (right click/add row). Set ALLUSERS property to 1 as instructed.
3. Find and select InstallExecuteSequence table in the left column. Find 3 Winhttp
Installer custom actions mentioned above in the list of actions. Ensure that their
sequence numbers follow right after sequence numbers of actions InstallInitialize
(usually 1500) and RemoveExistingProducts (usually 1525). By default they
might fall after 1500 but before 1525, so change them if needed.
4. Run msi validation via Tools/Validate to ensure your msi is correct.
Now your msi will perform correctly on all supported platforms.

When merging msxml4.msm SP1 you need to be aware of the following msxml4.msm
behavior.
If you merge msxml4.msm English into your msi and install it on the system that has
already an msxml4 with different language, you will overwrite the msxml4r.dll resource
file with the English version.
In order to prevent it, you may
- create all localized versions of your product and include msxml4.msm with
correct language in each version,
- or include all localized copies of the msxml4 into your msi package and install the
correct one depending on the language of OS
- or using Orca add a condition on the msxml4 component to not install if MSXML4
SP1 with any language is installed already.

Questions and Comments

Please send your questions and comments to the SOAP Toolkit public newsgroup:
microsoft.public.xml.soapsdk . See
http://msdn.microsoft.com/newsgroups/default.asp
for information on how to subscribe.