orca

In our build process there is currently the potential for non-code based files (such as image files) to be added to our web project, but not included in the MSI installer built by WiX. To help prevent this, I want to perform the following in the AfterBuild target for our WiX project: Get a count of all files built (output from web deployment project) Get a count of all files built into MSI (from "File" table in MSI) Compare counts and fail build if they don't match If I fire up Orca I can easily see the File table and count, but I don't know how to automate this from MSBuild. Is there some API

I have a MSM file from a third party tool. We customize the MSM with a small script and this tool is integrated into our installer and works fine. All modification is done with VBscript using COM and "WindowsInstaller.Installer" But sometimes our support needs just this tool as standalone installer package. Is there a simple way to convert a MSM file into and full installer MSI package on the command line? Using VBscript or the COM Module with the "WindowsInstaller.Installer" is OK. Knowing the way how to to convert it, I would also write a small C++ program doing performing the changes and

We have an application to be run on startup that allows many installed files to be changed after installation. We are trying to turn off the self-healing mode by setting the DISABLEADVTSHORTCUTS=1 property in Orca. However, no shortcuts are being created when this property is set. All the information I've seen indicates that we should be able to create "non-advertised" shortcuts with DISABLEADVTSHORTCUTS=1 set. Any ideas? I have verified that the shortcuts are created correctly if DISABLEADVTSHORTCUTS is left unchanged. If you're creating a Setup and Deployment project in Visual Studio 2008,

Many of our customers have access to InstallShield, WISE or AdminStudio. These aren't a problem. I'm hoping there is some way I can provide our smaller customers without access to commercial repackaging tools a freely available set of tools and steps to do the file replacement themselves. Only need to replace a single configuration file inside a compressed MSI, the target user can be assumed to already have Orca installed, know how to use this to customize the Property table (to embed license details for GPO deployment) and have generated an MST file. Disclaimer : this is very similar to