I know it is supposed to work (saw the fixed bugs on it) but I needed a
sanity check just to confirm with someone else that using WiX v3.5 and
DTF with targeted .NET framework of 4.0, that it works for them and I
must be doing something wrong =]
Hi all,
I am attempting to build a bootstrapper for my wix installer in order
install another program our customer wants deployed along with ours. I've
been given the .msi file.
Here's the error / warning I'm getting:
warning MSB3155: Item 'Network.Configurator' could not be located in
'C:\Progra
ServiceControl rows don't have a condition. They are based on the action
state
of the component to which they are associated. That component can have an
action and I suppose it could also be a transititive component ( for example,
use the condition Installed so that it doesn't get installe
Is there a way to set a condition on a ServiceControl entry? Like having a
service start after a
repair but not on the initial installation? Would this best be handled with
separate ServiceControl
entries in separate components, with conditions on the components?
Thanks,
Rob
--
The complete error message would also be useful. It's probably error 1402, and
that should also include a Win32 error number somewhere.
Phil Wilson
-Original Message-
From: Calin Iaru [mailto:ca...@dolphinics.no]
Sent: Friday, March 25, 2011 2:37 AM
To: General discussion for Windows
Hi,
I'm installing 1-10 Features.
FeatureInstance1
FeatureInstance2
FeatureInstance3
FeatureInstance4
FeatureInstance5
FeatureInstance6
FeatureInstance7
FeatureInstance8
FeatureInstance9
FeatureInstance10
Now I'm trying to uninstall a selected feature or add another on change.
I
I now also have a wixlib with the windows installer 3.1 package in it too.
Marvellous!
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: 25 March 2011 12:22
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] version comparisons in burn
After poking about the source code I have found the magic(tm).
DetectCondition='VersionMsi>=v3.1.4000.2435'
Where VersionMsi is a burn built in property (so i dropped my filesearch) and
v in front of a version makes burn evaluate the next bit as a version number.
Also it looks like literals shou
Not sure but have you tried it in the same format as
Package/@InstallerVersion:
http://wix.sourceforge.net/manual-wix3/wix_xsd_package.htm
So for 3.1, use 301. Etc...
Don't know about your second question.
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: 24 March 2
Hi everybody,
Thanks Tobias for his answers.
@Tobias: I not sure if it makes any difference, but I intend to use LCID
without using WixUIExtension. Is your list of supported languages is also valid
when one doesn't use the translated UI?
Another question is to the whole community. Does anybody
Oops, that's what you get for skimming help and source files.
In closer examination I do actually use ComputerName, only one wix file has
LocalMachine and it is used in a Util:PermissionEx@domain which then resolves
to null and that works.
Scary.
Inherited code that 'works' can be fun.
Dave
-
Hi,
In addition to Bruce's suggestion, I recommend running Procmon
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx with Registry
accesses enabled.
Calin
-Mesaj original-
From: Bruce Cran
Sent: Thursday, March 24, 2011 4:24 PM
To: General discussion for Windows Installe
Hi Tobias,
In relation to a separate issue, a colleague asked all the developers at his
site to install our
driver and reports that about 1 in 10 fail, but a second attempt works fine.
Thanks for the link,
I'll check it out.
Rob
On 24/03/2011 21:03, Tobias S wrote:
> Hi Rob,
>
> Just some t
13 matches
Mail list logo