Bob,
You're exactly right in each of your comments. But they don't address
the root cause of the problem. The error messages I was receiving were
"red herring" messages. It seems I ran afoul of differences in the way
WiX3.5 and WiX3.6 interoperate with Visual Studio.
Starting with a large project that built perfectly under WiX3.5, I
installed WiX3.6, expecting that everything would run with few, if any,
changes. WRONG!
The WiX3.6 documentation clearly states how each of the various WiX3.6
components operate. But I haven't located anything that addresses how
to convert an operational WiX3.5 project to a WiX3.6 project.
After rewriting the WiX3.6 project from scratch, it's now working.
Dave
-----Original Message-----
Date: Sun, 27 Nov 2011 22:02:43 -0800
From: Blair <os...@live.com>
Subject: Re: [WiX-users] Wix bug #1908338 regression in WiX 3.6?
To: "'General discussion for Windows Installer XML toolset.'"
<wix-users@lists.sourceforge.net>
Message-ID: <blu160-ds197c2d8a38147cec4d8cedcd...@phx.gbl>
Content-Type: text/plain; charset="us-ascii"
I would say that your use of <DefineSolutionProperties> is unrelated to
the "Unresolved reference" error, except for the following: The
"Undefined preprocessor" error comes from candle, and the "Unresolved
reference" error comes from light, and since candle runs before light,
that error stops the build before the other error could ever surface.
Are you harvesting your C# projects from your WiX project? How are you
"handcrafting" your references? What settings/properties have you set
wrt your harvesting?
That is where I would start my investigation.
Blair
From: David P. Romig, Sr. [mailto:d...@tcsc.com]
Sent: Thursday, November 24, 2011 7:17 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Wix bug #1908338 regression in WiX 3.6?
Bob,
Thanks for your reply, but the problem is not related to the DDK or C++
projects. The DDK and C++ project setup is handled separately through
hand-crafted references in their respective .wks files. Under WiX 3.5
this project built successfully using the same .wxs and .wixproj files.
With WiX 3.6, when the element <DefineSolutionProperties>is 'False' or
omitted, an IDE build or command line solution build raises the error
"Unresolved reference to symbol 'WixComponentGroup:<C# module
name>.Binaries' in section 'Fragment:'.
D:\Projects\trunk\src\app\Deployment\WixSetup\<C# module name>.wxs" for
each of the dozen C# modules referenced in the .wixproj file.
When the element <DefineSolutionProperties>is 'True', an IDE build or
command line solution build raises the error "Undefined preprocessor
variable '$(var.SolutionDir)'.
D:\Projects\trunk\src\app\Deployment\WixSetup\PrinterManager.wxs"
PrinterManager.wxs is the only project file containing a reference to
the$(var.SolutionDir) variable.
Could this be an issue in the wix2010.targets file?
Thanks,
Dave
------------------------------
Date: Wed, 23 Nov 2011 22:56:44 -0500
From: Bob Arnson <b...@joyofsetup.com>
Subject: Re: [WiX-users] Wix bug #1908338 regression in WiX 3.6?
To: wix-users@lists.sourceforge.net
Message-ID: <4ecdc07c.2070...@joyofsetup.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 23-Nov-11 18:31, David P. Romig, Sr. wrote:
> After installing WiX 3.6 beta, I'm receiving the error as described in
bug report 1908338. Is this a regression?
That bug is about what happens when the values aren't defined (i.e.,
CNDL0150).
> The solution contains 12 C# projects, a DDK project in C and a couple
C++ projects in addition to the WiX project. The build environment is
Visual Studio 2010 version 10.0.31118.1 SP1Rel.
How is your C project built? WiX only supports project reference
variables for MSBuild projects, so a Makefile project wrapping a DDK
dirs/sources project won't work.
--
sig://boB
http://joyofsetup.com/
------------------------------
The WiX-devs archive lists failure to resolve "$(var.SolutionDir)" as
bug
1908338.
After installing WiX 3.6 beta, I'm receiving the error as described in
bug
report 1908338. Is this a regression?
Light raised the error "LGHT0094: Unresolved reference to symbol
'WixComponentGroup:Utilities.IO.Binaries' in section 'Fragment:'" for
each
ComponentGroupRef and the warning " C:\Program Files
(x86)\MSBuild\Microsoft\WiX\v3.x\wix2010.targets(1226,5): warning :
Solution properties are only available during IDE builds or when
building
the solution file from the command line. To turn off this warning set
<DefineSolutionProperties>false</DefineSolutionProperties>
in your .wixproj file.
[D:\Projects\trunk\src\app\Deployment\WixSetup\WixSetup.wixproj]".
So in the initial PropertyGroup of the wixproj file I added the element
definition "<DefineSolutionProperties>False</DefineSolutionProperties>".
While this resolved the LGHT0094 error, the WiX project now fails to
build
with the error "error CNDL0150: Undefined preprocessor variable
'$(var.SolutionDir)'."
The solution contains 12 C# projects, a DDK project in C and a couple
C++ projects in addition to the WiX project. The build environment is
Visual Studio 2010 version 10.0.31118.1 SP1Rel.
How can I use the project references and variables as listed in the
documentation?
Regards,
Dave
------------------------------------------------------------------------
----
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
