Found the solution to my own problem.
The custom action had a config file for the dll, but it wasn't named
CustomAction.Config.
I added a CustomAction.Config file to the project, set it to a build action
of "Content" and specified that the custom action should run against
framework 4.0
Which s
Interestingly if I add the 3.5 framework to the machine I get a different
error in the log:
Action 10:41:33: GetOfficeVersions.
Action start 10:41:33: GetOfficeVersions.
SFXCA: Extracting custom action to temporary directory:
C:\Users\DEVELO~1\AppData\Local\Temp\MSI806C.tmp-\
SFXCA: Binding to CL
I am having a problem with a custom action in my Wix installer, on a Clean
Install of Windows 8.1.
The machine has .NET Framework version 4.5 installed.
My custom action dll targets Framework 4.0 and works on a Windows 7 machine
( though this also has the 2.0 Framework installed ).
The config fo
I hit a similar problem and managed to fix it:
In the Process of the Build Definition, under advanced, change the MSBuild
Platform from *Auto* to *X86*. This forces the build to use the X86 version
of MSBuild, which in turn can run Heat.exe
Hope this fixes your problem.
--
View this message i
4 matches
Mail list logo