0
votes
[widcomm] Provide Windows Installer modules to aid installing dependencies

Description

We've done work to make the dependency checking easier for the Widcomm dependencies, so that we don't need the extra btwapi.dll file, but only the ubiquitous wbtapi.dll; and that we list any that are missing.  However we also depend on the VC++ Runtime, and that's something that changes (on the build machine) whenever a security fix or a new version of VC++ is installed.
We can provide a "Merge Module" (.msm) that includes the dependencies, and the end-developer can reference that from a Installer script to ensure they're installed at runtime.

File Attachments

No files are attached

Comments

wrote Jan 21 at 3:10 PM

Initial version provided in r63447.  Added two project:

"Setup32feetWidcomm" a Merge Module (.msm) -- which references the output from the 32feetWidcommWin32 project.  Is that enough to get the CRT dependency, or does one need to manually add a reference to the CRT Merge Module itself?

"CheckSetup32feetWidcomm" (.msi) which runs that merge module, and thus installing 32feetWidcomm.dll to a dummy location, and hopefully(!) installing the CRT too if not present.

 

Haven't tested this on a clean machine yet.  Has anyone got a suitable machine?


Updating...
© 2006-2010 Microsoft | Get Help | Privacy Statement | Terms of Use | Code of Conduct | Advertise With Us | Version 2010.8.10.17093