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
Any special way you have to open the CA dll with winzip? It's telling me
the file is not a valid archive.
We're running build 3.0.4207.0 of Wix.
-Tina
On Wed, Jun 17, 2009 at 11:32 AM, Christopher Painter <
chr...@deploymentengineering.com> wrote:
>
> YEs, you can open the resultant CA dll with
YEs, you can open the resultant CA dll with Winzip and you'll see your files.
BTW, what build of WiX are you on? There were a few issues in older builds
that have been resolved.
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good th
4 matches
Mail list logo
