I have created an MSI using WIX. This is working fine for
install/Un-install.
When i tried to re-install the MSI it shows lot of errors. from the log it
shows that could not register component.
ComponentRegister(ComponentId={A35FD4BC-66CA-4BE0-BCBA-EDEA2DFC7FD3},KeyPath=C:\Program
Files\Common
F
Classification: Public
For one thing you FOO property from your parent project is no longer FOO, in a
merge module it takes on the merge module's GUID so your property is now
FOO. as per your log:
FOO.F5F26EB0_E10F_4C42_9337_E3138BE966BC
To fix that in your merge module add:
I am passing a pr
Okay I am trying this out and I can not seem to get it working.
We are using WiX 3.7 and all it seems to do is delete the property. Maybe I
am missing something really easy and it is just escaping me. Here is what I
have:
In Merge Module:
It doesn't sound like your problem is with Java being a service, but in case
you have trouble with however your Java programs are bundled into exes to run
as services and are looking for an alternative, thus far I've found the Java
Service Launcher (http://jslwin.sourceforge.net/) works very wel
Hm, interesting. Assuming you are right and this is what's going on, I don't
think all four services are sharing jsl.exe, because it is only used to create
(or remove) Java-based services. Wouldn't the exe actually be java.exe, because
my services are Java programs? If so, I'm not sure how to te
Yes, but think about what happens if someone passes REINSTALL=ALL on the
command line.
--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack Henry & Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Mes
What if I were to split my installer into two features? Is it possible to
define element to create a patch for just a feature (and leave
other feature/components untouched)?
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: Tuesday, June 18, 2013 12:47 PM
To:
Because I started the installer before burn was available. Nor are the 32-bit
installers identical because some 32-bit third-party products we interface with
do not work on 64-bit platforms due to device drivers (which must be 64-bit).
We are also not using Java. In our case it's native code. Ou
I believe your /q parameter is instructing the exe package not to show a UI.
-Original Message-
From: Karl Werner [mailto:karl.wer...@gmail.com]
Sent: Tuesday, June 18, 2013 2:49 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Show UI during ExePackage in
Is there any way to show an ExePackage UI? In my case I'm downloading and
installing the .Net 3.5 Framework with this stuff:
http://go.microsoft.com/fwlink/?linkid=118076";
InstallCommand="/q /norestart /lang:ENU"
RepairCommand="/q /norestart /
Not during a patch without some trickery. A patch is effectively a Repair of
the effected feature, and if that component is in an effected feature, it's
going to be reinstalled.
I handle encryption/decryption for both my passwords and my connection strings
by harvesting them directly (while en
So I've cobbled this together from a couple of different segments I found
googling. It downloads .Net 3.5 SP1 and installs it (if needed)
http://go.microsoft.com/fwlink/?linkid=118076";
InstallCommand="/q /norestart /lang:ENU"
RepairCommand="/q
Classification: Public
I have a client add in for Office
There are 60 + files, only 3 of them are 64 bit
So the 64 bit installer installs only 3 64 bit files and the rest are 32 bit
The 32 bit installer installs all 32 bit files...
(the add on is based on the bitness of Office not the OS) so yo
Thanks for the quick response...
According to documentation, if a Component is marked as Transitive='yes', it
will uninstall the component if the condition becomes 'False'. I don't want to
uninstall the component; I want to just leave it as is. Is that possible?
I know the persistent pattern
But why would you make a 64bit installer that installs both, and a second 32
bit installer. I fail to see the benefit of that vs a pure 32 bit installer
and a pure 64 bit installer, and then utilize burn to install them when needed.
If the files are in fact identical, you can go one step furth
Because the condition is not re-evaluated once it is installed unless the
component is marked Transitive.
I would recommend avoiding marking it Transitive and saving and restoring the
properties necessary for that component to work. In my experience, that is
best practice.
--
John Merryweathe
Thanks for the explanation.
-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: Monday, June 17, 2013 1:52 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patching error
George,
On initial installations Windows Installer seems to b
I have following component that I only want to execute during a new install.
When I do a patch (msp file), I don't want to run this code, since I don't have
a valid default [SERVICEACCOUNT] value. Still, the code executes and I get a
failure at ServiceInstall. Why isn't my working?
I use a WiX preprocessor variable for the Win64 attribute value so I can set it
in one spot when using the same source for generating a 32-bit and a 64-bit
MSI. That makes it easy e.g. Win64=$(var.Win64).
Daniel Madill
-Original Message-
From: Tim Hawes [mailto:haw...@anx.com]
Sent: Ju
Jacob Hoover is not correct as far as I can tell. I install to both the 32-bit
and 64-bit Program Files folder from a 64-bit MSI. I also pass the ICE
validation tests when building the MSI. I don't believe anything is off-limits
to a 64-bit installer.
Daniel Madill
-Original Message-
F
Classification: Public
You are correct, you CAN install 32 bit components in a 64 bit MSI, you CANNOT
install 64 bit components in a 32 bit MSI
I do this :)
Steve
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: June-18-13 2:17 PM
To: General discussion for Win
Wesley Manning writes:
> Curiosity got better of me. It seems that for a 64bit MSI Win64=yes is
> assumed so you only need to set the Win64 attribute (= no) for the 32bit
> components.
>
Apparently, it is NOT assumed for . I've spent half the
day spinning my wheels on that one today.
>
Wesley Manning writes:
> AFAIK you can have 64bit MSI install 32bit components. But a 32bit MSI can't
> install 64bit components. There is a 64bit attribute on the component to say
> if its 32bit or 64bit... Just from memory, never had to do this.
>
That's what I thought to be the case as w
Curiosity got better of me. It seems that for a 64bit MSI Win64=yes is assumed
so you only need to set the Win64 attribute (= no) for the 32bit components.
-Original Message-
From: Daniel Madill [mailto:dan.mad...@quanser.com]
Sent: June-18-13 3:23 PM
To: General discussion for Windows
I install 32-bit components using a 64-bit MSI all the time in order to have a
single MSI that provides support for our APIs to both 32-bit and 64-bit
applications running on a 64-bit O/S. It works just fine. I use WiX
preprocessor directives to build a pure 32-bit MSI for 32-bit platforms and a
AFAIK you can have 64bit MSI install 32bit components. But a 32bit MSI can't
install 64bit components. There is a 64bit attribute on the component to say
if its 32bit or 64bit... Just from memory, never had to do this.
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenh
Yes,
You may want to have a look at the RollbackBoundary element.
-Original Message-
From: Wang, Miaohsi [mailto:miaohsi.w...@invensys.com]
Sent: Tuesday, June 18, 2013 11:24 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Automatic rollback on a se
Hi Blair,
Sorry, I was looking at the wrong file. Please ignore my previous mail. Below
is the part of the logging that you wanted to take a look. I can see a few
errors here, including my install program Client.msi. Can the failure of
Client.msi installation cause the setup prerequisite to rol
As far as I am aware, it is not possible/supported to install 32 bit components
in a 64 bit MSI. There are unsupported hacks out there, but they would fail
ICE validation and wouldn't be Logo certified.
If you already have a 64 bit and 32bit MSI, and the 64 bit MSI installs only
64bit componen
My understanding is that a 64bit installer can install 32bit binaries? I
am using this just for 64bit systems. I am already building a separate
32bit installer for 32bit systems (which only needs to test for JRE
version). The problem I describe below is a 64bit installer which must
determine which
Hi Blair,
Thank you for your help. The log file seems to indicate that the installation
completed successfully, as shown below by the last part of the log file. Please
let me know what else to look for.
Thanks a lot,
Miaohsi
MSI (s) (48:B8) [15:30:06:234]: Executing op: ProductPublishClient(,,
You need 2 MSI packages, one for the 64 bit components and one for the x86
components. You can utilize burn to do the bitness of the OS test and then
decide which installer to invoke.
-Original Message-
From: Tim Hawes [mailto:haw...@anx.com]
Sent: Tuesday, June 18, 2013 8:38 AM
To: Gen
I have a product that will use a 64bit installer. It uses an exe
wrapper
for the jar files so that the programs can be entered as Windows
services and the config programs can run from the Start menu. The
wrapper requires different binaries for the type of JVM installed,
32bit
executables for runn
Hi
you're right, thanks.
I used this:
(SampleMsiInstalledState = 5) AND (SampleMsiInstalledVersion >=
v$(var.BaselineVersion))
do determine whether the previous servicePacked version of the msi in the
bundle was already installed. the SampleMsiInstalledState variable pr
You need xmlns:bal="http://schemas.microsoft.com/wix/BalExtension"; in the Wix
element.
And then:
-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: June-18-13 6:04 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Suppress options
I was wondering if anyone with more WiX experience than me would have any
bright ideas about a problem I currently have...
I have a bootstrap package that installs .NET Framework 4.0 (if required), then
SQL Server 2012 Express Edition (32 or 64 bit as applicable) and finally my
app's MSI.
All
Hello,
Could you please give me some tips or solution how to prevent from
uninstalling package in bundle at the end (that is not being upgraded and is
exactly the same like in previous setup).
I was trying to create dependency in registry by "Provides":
I checked that key is created
I haven't played around with the standard BA much but wouldn't changing the
theme work?
Blair
> From: davidm...@omprompt.com
> To: wix-users@lists.sourceforge.net
> Date: Thu, 13 Jun 2013 13:15:41 +0100
> Subject: [WiX-users] Suppress options in bundle
>
> Hi all,
>
> I am trying to hide the
The burn log (look for IntelaTrac_20130617152938.log) will tell you which
package's error caused the rollback. Then you can look in that package's log to
see why it failed.
Blair
> From: miaohsi.w...@invensys.com
> To: wix-users@lists.sourceforge.net
> Date: Mon, 17 Jun 2013 18:53:24 -0400
>
Any of the MSI APIs for accessing binary data in tables (COM - see the VBS
samples in the SDK, C# - see DTF, C/C++ - see the recordset APIs involving
streams) running queries against that table should work.
Yes, MSI files are based on OLE Structured Storage but with some
modifications/alterati
Please look and see if it could possibly be
https://sourceforge.net/p/wix/bugs/3279/
Blair Murri
> Date: Thu, 13 Jun 2013 13:11:11 +0100
> From: br...@cran.org.uk
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Burn: installer doesn't restart after reboot when
> variables are spe
The standard BA supplied by WiX uses and evaluates it right
after detection before planning. The one used to install the toolset also uses
that same tag. You don't need a custom BA to use (although a
custom BA would need to be coded to use it). A custom BA doesn't need
(unless it deliberatel
Restart manager in your situation is probably working something like this:
Look at each component that is being removed
Look at each and every file in each of those components
Look at each and every process holding any of those files open?
Is that process's binary the keypath of any component tha
43 matches
Mail list logo
