Hi All,
I have a problem in using condition. I have used the Condition like
below. It works fine While installing, But after installing if I tried
to uninstall the condition is getting failed and could not able to
uninstall. Please help me out in this regard .
UDDIDBSERVICE
I also had trouble finding a decent bootstrapper. Nothing cheap or
free had the flexibility we needed, so ended up settling on the
bootstrapper that ships with "MSI Factory". Money well spent, even if
we are only just using the bootstrapper :)
2009/8/5 DEÃK JAHN, Gábor :
> On Wed, 5 Aug 2009 01
I probably shouldn't even reply here as this just sounds like a
really, really, really bad idea. I'm hoping this is for an internal
application for an internal business requirement, and not for any
publicly released software.
Hiding the uninstall button is easy, just use ARPNOREMOVE.
If you're re
You'll want a separate script (language doesn't matter, just whatever
you're familiar with) that can be called as part of your build process
to extract the value from the C file and then simply pass it in as a
variable when launching WiX.
I'm using Nant, and have a bunch of scripts to extract info
Did you remove any Components from Feature_D, or did you change any component's
guid (including any changes that would cause an autogenerated guid to be
different)?
That is the most likely cause. Elsewhere in the log you would possibly see
lines that contain "SELMGR" describing why things don't
I wouldn't expect heat to work with DCOM type registration. I would
start by looking at the CLSID entry in the registry, most of what you
need is there. Another option is to use something like regspy to see
what entries are written when you manually register the component or run
dcomcnfg.
I know t
I found something very interesting in the log that is probably causing this.
MSI (s) (2C:3C) [13:01:48:039]: Feature: Feature_A; Installed: Absent;
Request: Null; Action: Null
MSI (s) (2C:3C) [13:01:48:039]: Feature: Feature_B; Installed: Local;
Request: Absent; Action: Absent
MSI (s) (2C
I'd like to show dialog when user presses Next button on welcome page
warning user if some file not found. But it doesn't work. When I hit Next it
just goes to next page.
Here what I have:
1
1
Filek was not found. Please
They are native code libraries used both in making some of the interop for
the WiX build tools as well as the custom actions incorporated in several of
the supplied extensions.
They are in the distribution because they supply a good set of solid tested
code for helping building native dll custom a
The only problem with that is when I use Heat.exe there are no registry
settings exported since the exe file is created with a third-party
component that handles the registration.
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Tuesday, August 18, 2009 2:
Hi:
I have two questions:
Can someone tell me what wca and Dutil are? I realise they are a set of
functions, but where do they help wix developers?
Secondly, is there a reference as to what functions are available? I
could browse the source but if there's a quicker way of finding out the
funct
I'll gather up some more logging. Thanks Blair.
As far as the sequence, I tried between InstallValidate & InstallInitialize
for one run, and also tried bumping it after InstallInitialize and before
any other in-script execution CA. I'd rather the product be removed first
before installing the n
Fairly new to working with setupbld.exe and finding that it doesn't
handle errors very nicely.
I currently have the bootstrapper combining two MSI's (Visual Studio
setup projects).
The problem is the first msi is failing because it is a newer version
with the same version number (its a build v
Hello,
When using InstallShield, I can add a schema version information to any sql
script I want the setup to run. When executed, InstallShield creates an
"InstallShield" table to the target database if it does not exist yet and adds
one row with the schema version I added to the script. If the
14 matches
Mail list logo
