I narrowed it down to one use case, but I don't know why this is happening:
It's when I have a custom action project included in the MergeModule, and I 
define a custom action that calls it (you don't even have to schedule it in the 
execute sequence).
Then if I make an irrelevant property as Secure, it fails. The following 
example replicates this (in a merge module project):
<?xml version="1.0" encoding="UTF-8"?>
<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi";>
  <Module Id="TestModule" Language="1033" Version="1.0.0">
    <Package Id="{76C85BEC-DE96-4D24-AB01-F04A05E8F515}" Manufacturer="Foo" 
InstallerVersion="200" InstallScope="perMachine" Platform="x86"/>

    <Directory Id="TARGETDIR" Name="SourceDir">
      <Directory Id="ProgramFiles64Folder">
        <Directory Id="INSTALLDIR" Name="Foo">
          <Component Id="cmp1" Guid="{6102D687-A7E8-475E-85FA-346EACE99C8A}">
            <File Id="testFile" KeyPath="yes" Checksum="yes" 
Source="C:\test.txt" />
          </Component>
        </Directory>
      </Directory>
    </Directory>

    <!--This fails. If i remove the Secure attribute, it will work-->
    <Property Id="PROPERTY1" Value="1" Secure="yes"/>

    <!--Custom Action Definitions. The Dll file, and the Custom action to 
call-->
    <Binary Id="CustomActions" 
SourceFile="$(var.CustomAction.TargetDir)$(var.CustomAction.TargetName).CA.dll"/>
    <!--THIS SEEMS TO BE THE PROBLEM. IF I REMOVE THE LINES BELOW, I CAN SET 
THE PROPERTY ABOVE AS SECURE-->
    <CustomAction Id="DeleteOrphanedFiles" BinaryKey="CustomActions"
                   DllEntry="DeleteUnusedFilesOrDirectoriesForConnector" 
Execute="deferred" Return="check" HideTarget="yes" Impersonate="no"/>
  </Module>
</Wix>

Strange right?

-----Original Message-----
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: 03 October 2012 04:18
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Adding the Secure attribute in a Property fails to 
build merge module in 3.6

On 02-Oct-12 11:23, Stelios Kyprou wrote:
> After upgrading from 3.5 to 3.6, when building a merge module I get the 
> following error:
Sounds like a bug. Please file with a small merge module project.

--
sig://boB
http://joyofsetup.com/


------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
________________________________

This message w/attachments (message) is intended solely for the use of the 
intended recipient(s) and may contain information that is privileged, 
confidential or proprietary. If you are not an intended recipient, please 
notify the sender, and then please delete and destroy all copies and 
attachments, and be advised that any review or dissemination of, or the taking 
of any action in reliance on, the information contained in or attached to this 
message is prohibited. Formicary cannot guarantee that this message is secure 
or free of errors or viruses.

------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to