Hi there,
I'm seeing the following error using WiX build 3.0.5308 or 3.0.5315 in
Visual Studio 2008 (but it works fine in 5301 and prior).
C:\Program Files\MSBuild\Microsoft\WiX\v3.0\Wix.targets(792,5): error
MSB4036: The "ResolveNonMSBuildProjectOutput" task was not found.
Check the following:
1
Riyaz Mogharabin wrote:
> I've heard that putting the files in more than one cabinet can be helpful.
> Is that right? And how much does it help?
>
http://www.joyofsetup.com/2008/03/29/wix-performance-tip-use-multiple-cabinets/
--
sig://boB
http://joyofsetup.com/
---
Riyaz Mogharabin wrote:
> In the MSDN is said that >< between the strings checks the left string and
> returns TRUE if it contains the right string.
>
Does it not work? What have you tried?
--
sig://boB
http://joyofsetup.com/
Phil Sayers wrote:
> Is there a way I can Enable the Next button as soon as the first character
> is entered into the third textbox?
>
No. MSI UI doesn't work that way.
--
sig://boB
http://joyofsetup.com/
--
Crysta
Shawn Dwyer wrote:
> If I schedule a custom action for OnExit, is there an easy way from inside
> the custom action to determine if it was being called for OnExit="success",
> "error", or "cancel"?
No. You need multiple entry points that wrap a common shared function.
--
sig://boB
http://joyof
Jeff Reed wrote:
> How can I use the same screen to push to a different set of properties?
>
Use indirect properties. See BrowseDlg.wxs in the WiX source for an example.
--
sig://boB
http://joyofsetup.com/
--
Cryst
barry wrote:
> Maybe the problem lies in the way I am making my bootstrapper by editing the
> wixproj file..
>
> What is the "right way" to add a bootstrapper?
>
Sorry, I don't use the .NET bootstrapper so I don't know. Have you tried
using an entirely separate .proj file rather than editing t
David Bartmess wrote:
> Is there a way inside wix to uncheck a checkbox? Especially if it can be
> conditioned off another control?
>
Set or clear the property associated with the checkbox.
--
sig://boB
http://joyofsetup.com/
---
Crusty Applesniffer wrote:
> I wonder if there isn't a bug in "WixUI_Advanced" flavor with 64bits.
>
> The suggested folder in the destination folder dialog is "C:\Program Files
> (x86)\My App" but when I change the flavor into WixUI_InstallDir (and set
> the WIXUI_INSTALLDIR property), the suggest
Brooke Philpott wrote:
> When I do a fresh install I'm using a bootstrapper to launch the msi
> with admin rights so I can perform a LogonUser call in order to validate
> the account used during the execution phase for the service. I want to
> do that validation up front so I don't get an error dur
Hi Neil
Well I had another WiX project that was working fine - and the only
difference was the KeyPath setting for the parent File element (since the
shortcuts are nested) as well as the name of the Shortcut - which I changed
from the variable I was using for the product directory - to a dedicated
Fixed. Made the File element for the nested shortcut the KeyPath and changed
the name of the shortcut property - and the icons are appearing correctly
now. Not 100% sure if this was a WiX or Windows 7 issue.
-Original Message-
From: Anthony Bouch [mailto:anth...@abouch.com]
Sent: Sunday,
I have seen the "white icon" problem before (on Vista), in fact the WiX
3.0 install always shows white icons for the documentation until you
first use them. That is it did until the latest release now they stay
white. I think this is a bug but I am not sure if it is a Windows
Installer bug or WiX.
13 matches
Mail list logo
