Got it. It's a bug. The SetProperty element creates simple references now so
that you can fragment them from the actions they come before or after.
Unfortunately, the simple reference for custom actions is created
incorrectly and will never be satisfied.
If you could open a bug on this issue, that
Putting it in wxs as fragment also gave same error. I am stuck .
On Sat, Jul 17, 2010 at 11:11 AM, Bhaumik Barot wrote:
> This structure worked fine with wix 3.0 .after upgrading to 3.5 and
> changing ref in wixproj file for 3.5 getting this resolved reference errors
> .
>
> Below is my include
This structure worked fine with wix 3.0 .after upgrading to 3.5 and changing
ref in wixproj file for 3.5 getting this resolved reference errors .
Below is my include file for custom action.
Bhaumik
On Sat, Jul 17, 2010 at 10:54 AM, Bhaumik Barot wrote:
> xml version="1.0" encoding="utf-8"?>
>
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-
What is in the .wxi file? Personally, I would take the out and
take whatever is in the .wxi file and put it in a Fragment element.
On Sat, Jul 17, 2010 at 7:58 AM, Bhaumik Barot wrote:
> I am new to Wix and upgraded existing wix 3.0 code to 3.5 as we are using
> VS 2010.
>
>
>
> I have my cu
I am new to Wix and upgraded existing wix 3.0 code to 3.5 as we are using
VS 2010.
I have my customaction.wxi That I am including in Product.wxs
Like this
NOT Installed
NOT
Installed
SQLINSTANCE_ISVALID = "0" AND NOT Installed
NOT I
6 matches
Mail list logo