Hi all,
We are using a debug build of WiX 3.6.3005 with a few changes compared to
standard source files
and have a problem on Windows 8 only with our bundle (managed UI).
After everything is installed (or uninstalled), the chainer seems to hang for
some time, and after a couple of minutes it sho
Take a look at WixBA (available in the WiX source files, it's the WiX installer
UI).
You will find the PlanPackageBegin handler in InstallationViewModel.cs (at
least for WiX version 3.6 this is true).
You can set in here the state of each package from your bundle (i.e. you can
always plan Launch
onBegin on
BOOTSTRAPPER_ACTION_MODIFY also...
If somebody sees something dangerous with my particular "modify" usage or burn
code correction, please let me know... :)
____
From: Adrian Gantoi
To: General discussion for Windows Installer XML toolset.
Sent: Tuesday
ER_ACTION_INSTALL in my bundle
"Modify" action ?
________
From: Adrian Gantoi
To: General discussion for Windows Installer XML toolset.
Sent: Tuesday, October 9, 2012 11:53 AM
Subject: [WiX-users] Burn bundle versions and BOOTSTRAPPER_ACTION_MODIFY
Hi all
Hi all,
I created a bundle that can install up to 5 different MSI packages (different
products).
The bundle allows the user to install / modify / uninstall / layout through a
managed UI.
"Install" allows the user to select which MSI packages should be installed,
"Modify" which packages to be in
Thanks,
Adrian
____
From: Adrian Gantoi
To: Rob Mensching ; General discussion for Windows
Installer XML toolset.
Sent: Monday, August 13, 2012 3:21 PM
Subject: Re: [WiX-users] Burn - multiple PackageGroupRef in Chain - download
issues
Hi Rob,
Thanks for your
Probably the safest place to link to is the Microsoft Download Center.
Go to http://download.microsoft.com, search for (e.g.) "Visual C++ 200x" and
you will get a list of results.
Locate what you need in here and click on download - most of these "download"
links will open a new page for the down
on the first package with more than 3 payloads...
I will keep looking for the problem with the completely downloaded packages
being removed from cache in such a case and send an email or create a bug in
case I spot the problem.
Thanks,
Adrian
From: Rob Menschi
Hi all,
I have a question on using burn for a multi package install with full download.
I have a chain of packages like below:
Each PackageGroup consists of a MSI and it's payloads. All have the DownloadUrl
data set - I deliver only the exe which should download
Hi all,
I have a problem which I cannot figure out - I created a bundle using WiX 3.6
(build 2803).
The UI is a WPF component so I had to request the install of .NET Framework 3.5
for this (UI modified from WiX installer UI - WixBA - changed target framework
to 3.5).
The bundle fails to install
Hello,
I am trying to build a setup using WiX 3.5 build (migrating from WiX 3.0).
This setup includes a melt generated wxs file (from a MSM).
I have a problem due to the fact that the MSM intends to grant access rights on
a particular folder it creates.
Due to this, in the generated wxs I have
ing"
Thanks,
Adrian
From: Bob Arnson
To: General discussion for Windows Installer XML toolset.
Sent: Tue, November 10, 2009 3:13:04 PM
Subject: Re: [WiX-users] Product uninstall problem when removing first a patch
Adrian Gantoi wrote:
> I also had a loo
Bob Arnson wrote:
> Search the log for SELMGR.
The log files do not contain it...
From: Adrian Gantoi
To: General discussion for Windows Installer XML toolset.
Sent: Mon, November 9, 2009 5:14:48 PM
Subject: Re: [WiX-users] Product uninstall problem w
h
Perchance did you remove any components in your SP2 patch?
Set MSIENFORCEUPGRADECOMPONENTRULES=1 in both commandlines when rerunning
the scenario. If you get an installation failure that should point you to at
least one component rule violation that will produce the effect you are
describing.
Hi all,
I have the following problem with our installer for which we deliver a service
pack (patch) setup.
We use for the setup and patch build the WiX build 3.0.4014.0.
Situation is as follows:
a) we built (and shipped) our product MSI (let's call it build 1.0).
b) we built (and shipped) a full
Hi,
I am not sure if your problem comes from this, but I experienced in the past a
similar problem with yours.
Windows Installer did not correctly resolve the real location of a folder in a
Repair/Uninstall scenario.
This happened to me for folders which did not have any files installed inside
e different, so this is probably a
different file. That means the file will be wrong for one of the products.
Adrian Gantoi wrote:
> Hi all,
>
> Still no answers for my problem below.
> Doesn't anybody have a clue of what's wrong (why is the wrong
> transform applied by
Hi all,
Still no answers for my problem below.
Doesn't anybody have a clue of what's wrong (why is the wrong transform
applied by the patch) ?
Thanks,
Adrian
Adrian Gantoi <[EMAIL PROTECTED]> wrote:
Hi all,
Sorry for being so "long"
From: Adrian Gantoi <[EMAIL PROTECTED]>
To: wix-users@lists.sourceforge.net
Sent: Tuesday, February 12, 2008 12:35:42 PM
Subject: [WiX-users] Single patch for multiple products
Hi all,
Sorry for being so "long" in describing my problem :), but...
I encountered a problem with ap
Hi all,
Sorry for being so "long" in describing my problem :), but...
I encountered a problem with applying a patch in the following scenario.
I have a setup project with 2 configurations which I build.
Configuration 1
- the product has the Product Id GUID1
- the product has a component with Id CO
b8b1-4dad3ba95bac)
It works by creating a component which has the folder (TDIR) as KeyPath.
Good results then after Repair.
Maybe it helps others in the future.
Thanks all.
Adrian
- Original Message
From: Bob Arnson <[EMAIL PROTECTED]>
To: Adrian Gantoi <[EMAIL PROTECTED]&g
,
Adrian
- Original Message
From: Bob Arnson <[EMAIL PROTECTED]>
To: Adrian Gantoi <[EMAIL PROTECTED]>
Cc: wix-users@lists.sourceforge.net
Sent: Sunday, October 7, 2007 8:11:04 PM
Subject: Re: [WiX-users] Customizable folder name written in registry - lost
(reverted to defaul
Hi all,
I came across a problem with my installer. WiX sources contents below:
As you can see, I have two components - a file and a registry value.
The file gets installed in [TDIR]\Sub
What you can do with MSI :
- create an installer which will install Win32 components on Win32 platforms
- create an installer which will install x64 and/or Win32 components on x64
platforms
You can't however create a single MSI for both Win32 and x64 platforms.
Because a MSI must be specified as "
Hi all,
I have a problem with understanding a MSI feature/behavior.
Below is the setup structure.
* Feature A
* ComponentGroupRef containing:
Component A
Executable
Advertised shortcut to executable, with exe arguments including
a file from "Component
then [FOUNDTABCTL32] will be
defined and the condition will hold, thereby setting the
FeatureToInstallWhenOCXMissing Level="0"
Tell me if this helps at all,
Alexei
Adrian Gantoi wrote:
>
> Hi all,
>
> I'm having a problem with correctly specifying the Feature's Co
ething like:
<[FOUNDTABCTL32]>
This way when the FileSearch finds something then [FOUNDTABCTL32] will be
defined and the condition will hold, thereby setting the
FeatureToInstallWhenOCXMissing Level="0"
Tell me if this helps at all,
Alexei
Adrian Gantoi wrote:
>
>
Hi all,
I'm having a problem with correctly specifying the Feature's Condition.
My goal - make a search of an ocx file, and if the ocx file does not exist on
the target computer,
keep a feature selected for installation.
If the ocx exists, the feature should be automatically deselected.
I'm curre
(hopefully
close) future?
Any chance of it becoming a "feature request" for WiX ?
Thanks,
Adrian
Adrian Gantoi wrote:
- I defined several Medias (several cabinets)
- I defined the Directory structure
- I placed all the Components within DirectoryRefs
If I set the DiskId attribute in th
Hi,
I need to build a project to output several cabinets.
At the moment I have a problem doing this because I found the following bug:
- I defined several Medias (several cabinets)
- I defined the Directory structure
- I placed all the Components within DirectoryRefs
If I set the DiskId attribute
Hi,
Can somebody solve this problem for the next build of WiX v3 ?
The warnings and errors are shown only with their numbers, the text of the
warning/error is not displayed if the project is built from within Visual
Studio 2005.
If built from the command-line, the warnings and errors are shown f
31 matches
Mail list logo
