David Gardiner wrote:
At a guess, I'd say it might be related to the changes made for bug 2786736
Agreed. I reopened the bug. Can you attach a /v:diag log of a
command-line MSBuild run? I suspect MSBuildToolsVersion is a value I
didn't expect.
--
sig://boB
http://joyofsetup.com/
hi all
i want to compose an msi which has two feature and four component
component would have any no o files..
i want the msi to be installed from FLASH drive...and one of the feature
should run-from-source..
after installation application should only when required component is
available in FLASH
If you want to build the project, manually go in and set the ToolsVersion
attribute to 3.5 of the Project tag in the votive project (.wixproj) file.
This task is in MSBuild 3.5, not 2.0.
I had the same problem.
I tried to send the same message earlier, but Cox munched my email. I hope
this
How do I clear the property? I tried setting it via a Property custom action to
But that doesn't clear the checkbxo.
Thanks for the help!
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Sunday, May 17, 2009 8:02 AM
To: General discussion for Windows Installer
The PermissionEx element map directly to the ACLs that you can set on a
registry key. Check MSDN to see the right combination for read of a
registry key (it's probably not just Read but also includes Enumerate
Subkeys or something).
Michael Bednarek wrote:
Hi all,
I am using the WiX 3.0
Scott Button wrote:
Yes, I have re-read the WiX.chm sections on multi-language builds. Also
read a number of blogs and the tutorial at blogs.technet.com/alexshev/ How
about another hint about how to diagnose the error:
candle.exe : error CNDL0288: The variable 'Configuration' with value
I am attempting to patch an existing web.config file with new web.config
settings. When I execute msiexec and pass in the msp file, the
util:XmlConfig patches are not being applied.
My Tools.v1.0.1.Patch.wxs file looks like:
*?xml version=1.0 encoding=UTF-8?
Wix
This isn't a common problem because everyone just lets the file versioning
rules take care of everything. If you have version 1.45 then you won't replace
1.49, and if you have 1.55 you will replace it - that's the built-in versioning
rule of Windows. Do you have other versions of these files
I used to have some MSMs created by Wise that had an entry in the directory
tree of INSTALLDIR. This entry didn't have modularization (i.e. no GUID
appended) and as such when I merged this MSM into an MSI, whatever value of
the MSI's INSTALLDIR was, I was able to use this propery in my MSM's
It would probably be helpful if you showed the code. Please show all
uses of the token 'Configuration' in the .wxs file which candle is
complaining about.
-Original Message-
From: Scott Button [mailto:scott.but...@sphericalangle.com]
Sent: Monday, May 18, 2009 7:02 PM
To:
Aha! Just saw this...
Setting the ToolsVersion fixes the first issue, but leaves me with a
bunch of ICE errors, which I've never had before
light.exe(0,0): error LGHT0217: Error executing ICE action 'ICE08'. The
most common cause of this kind of ICE failure is an incorrectly
registered scripting
Hi All,
Just today all of my wix projects started failing to build. I am not
aware of any new installation which could have affected this.
I have re-installed VS AND WiX, and still the problem remains.
C:\Program Files\MSBuild\Microsoft\WiX\v3.0\Wix.targets(789,5): error
MSB4036: The
Hi Guys,
I was wondering how do I re-open a bug in source forge tracker as it has
reached 21 days of inactivity. I only just tested it as I was unsure
what release the fix would be in and can confirm that it has not been
fixed.
13 matches
Mail list logo