On 17-Jan-12 17:16, Peter Hull wrote:
I'd still like to hear if anyone has any comments on a per-user
install which includes a device driver - is it always better to do it
per-machine.
Drivers are per-machine resources so a per-user installer that includes
one can't offer the benefits of
On 17-Jan-12 05:58, Per Næsgaard Andersen wrote:
[Mixed Platforms/Debug] [some
path]\Fls.Xxx.Install\Fls.Xxx.Install.wxs(58,0): error LGHT1056: The Property
table contains a row with primary key(s) 'MsiHiddenProperties' which cannot
be merged from the merge module '[some
Thanks!
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Saturday, January 21, 2012 1:51 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Wix Weekly Builds?
Just:
Hi, I'm trying to use this custom action so far without success as I don't
know how to pass the parameters to it.
http://code.dblock.org/Source/msiext/1.2/Docs/_win32_impl_8h.html#a427b16cc4d6285c4eac3227ac5723050
CA_API UINT __stdcall Win32_WriteFile ( MSIHANDLE hInstall )
Write to an ANSI
Hey!
Just tried out the weekly build 3.6.2520, I think there is a bug in the
wix.ca.targets.
I had to change these two lines:
WixTasksPath Condition= '$(WixTasksPath)' == '' AND
'$(MSBuildExtensionsPath32)' != ''
$(MSBuildExtensionsPath32)\Microsoft\WiX\v3.x\WixTasks.dll/WixTasksPath
Hi,
Thanks for the replay, you are right, removing the children from the
PatchFamily element does include everything.
But now I have a new problems :)
I get this error:
C:\Sample_1pyro.exe -v patch\patch.wixmsp -out patch\patch.msp -t RTM
patch\diff.wixmst
Microsoft (R) Windows Installer Xml
6 matches
Mail list logo