I have another merge module that adds custom actions after
CostFinalize so I thought there might be a clash somewhere. I removed
this other working module from the installer and the new custom action
showed up with no problems.
When I added it back in, the problem re-appeared. I noticed I was
gett
Strange. Try running light.exe with the -notidy switch and look for the
merge.log in the left over TEMP directory. It may point out a failure
during merge module merging.
Antony Walmsley wrote:
> I've got a custom action set up in my merge module as follows :
>
> SourceFile="$(env.VSBUILDPA
I've got a custom action set up in my merge module as follows :
$ComputerName=2
Looking in Orca at the msm file, I see that the CustomAction table and
the ModuleInstallExecuteSequence table have the custom action in them
as ex
However, looking in the msi file that uses
3 matches
Mail list logo