Hi,
Iam Having two msi,s.in one msi iam having 200 patches.i installed that.it
creates one msi in my control panel.iam going to install 2nd msi that is
having remaining patches.that should upgrade with the same name which is in
control panel.not to create another name.how is it possible..
Thanks
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
About:
"Or am I using BOOTSTRAPPER_ACTION_MODIFY incorrectly ?"
I am aware this is intended to be used to modify installed features of a MSI,
but I saw no initial problem in transforming my MSI packages into "bundle
features"...
Should I stick to planning simply BOOTSTRAPPER_ACTION_INSTALL in m
You can add the "log on as a service" privilege to a user without creating
the user when using the User element. In what way does this not work in your
situation ?
-Original Message-
From: Senthil Chandran [mailto:senth...@microsoft.com]
Sent: 09 October 2012 00:55
To: wix-users@lists.sou
http://wix.sourceforge.net/manual-wix3/major_upgrade.htm
-Original Message-
From: Chaitanya [mailto:chaita...@pointcross.com]
Sent: 09 October 2012 09:06
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] upgrade code
Hi,
Iam Having two msi,s.in one msi iam having 200 patches.i in
Hi I am having trouble with my transforms, I have my main installer but when
I transform it, it stays the exact same. I opened the transformed msi in
Orca and it showed all my changes but when it is run I get the main
installer and not my transformed one. Anyone know what would cause this to
occur?
What command line did you use to install ?
Does a verbose log mention the transform that's being applied ?
-Original Message-
From: Natalie Carr [mailto:natalie.c...@measuresoft.com]
Sent: 09 October 2012 11:34
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Transform not working
It seems that I found another "thing" which has the same problem: DISM API
(http://msdn.microsoft.com/en-us/library/windows/desktop/hh824790.aspx).
It also requires elevated permissions (even to get info about installed
windows features).
Best Regards,
Igor
-Original Message-
From: Rob Me
Hi,
I checked that path but iam unable to upgrade to my exsisting msi..
Thanks,
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: 09 October 2012 14:50
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] upgrade code
http://wix.
I used Orca to create the transform and save the new transformed MSI. It was
when I tried to run that newly saved transform.
The main installer was already installed and when I uninstalled it, it
worked as it should. Is this a limitation of the transforms that they cannot
be run on an MSI that is
Just filed a bug for the BOOTSTRAPPER_ACTION_MODIFY / MajorUpgrade combination
- #3114.
Even if I misuse BOOTSTRAPPER_ACTION_MODIFY, somebody using it correctly ("as
designed") may still have this problem :).
Also rebuilding WiX/burn to write reg values in RegistrationSessionBegin on
BOOTSTRAPP
Can you give more information ? Is there an error message ?
-Original Message-
From: Chaitanya [mailto:chaita...@pointcross.com]
Sent: 09 October 2012 12:34
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] upgrade code
Hi,
I checked that path but iam u
Hi,
using PowerShell you won't need admin permissions to enumerate this. In my
installer I start a new process which hosts a PowerShell runspace. The new
process is required because the Burn bootstrapper does not run as X64 process.
However, this is required for the ServerManager snapin. The pr
I doubt I'd be much help coding this, but I have talked to my tester and I am
willing to code up one of our products to test burn multi-instance and he is
willing to test it.
Tyler Reid | Operations and Infrastructure | Accenture Software | P&C Insurance
1807 Jones Street | Bolivar, MO 65613| U
There is no guarantee that PowerShell is installed. For example on Windows
Server 2012 Core it is not a default feature.
Best Regards,
Igor
-Original Message-
From: Henning Krause [mailto:m...@henningkrause.eu]
Sent: Tuesday, October 09, 2012 1:52 PM
To: General discussion for Windows In
That clearly saying that another version is running
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: 09 October 2012 17:28
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] upgrade code
Can you give more information ? Is ther
It is not possible to run two installers at the same time. Wait until one
installer has finished before starting the other.
If you believe that you do not have two installers running at the same time,
check Task Manager and see if msiexec.exe is there. It's safe to kill
msiexec.exe if no installati
We have a situation where the original install uses a property named 'DBTYPE'
to determine optional nstall of files. On the base install, some properties
are written to the registry, but DBTYPE is not.
In the patch this is having a negative effect because the DBTYPE is defaulted
to '1' and whe
DBVERS
The condition means "if DBVERS has any value". An empty string is the same as
no value and is equivalent to a property that doesn't exist.
-Original Message-
From: Justin Hull [mailto:justin.h...@assetpoint.com]
Sent: 09 October 2012 17:01
To: General discussion for Windows Instal
Hi everybody,
I am experimenting with building a simple setup on tfspreview, and I've
run into a problem. The setup BTW, consists of a single feature, one
component and a single file.
I have checked-in the binaries into src control and made the necessary
changes in the project file to set the Wix
For those who are searching for an answer, this is what has worked for us:
private void PlanPackageBegin(object sender, PlanPackageBeginEventArgs e)
// if this is the package, which has optional features
if (e.PackageId.Equals("",
StringComparison.Ordinal))
{
// if the action b
> -Original Message-
> From: Shane Corbin [mailto:shane_cor...@selinc.com]
> Sent: Friday, October 05, 2012 18:07
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] DIFxApp and upgrades
>
> Hey James,
>
> Did you ever get any resolution to your problem regarding scanning for
Is this a major upgrade scenario? I would hope you aren't planning on invoking
the uninstall of the previous version from a CA.
If it is a Major Upgrade, if you were lucky enough to have this old data in its
own feature then you could look at the RemoveFeatures attribute of the
MajorUpgrade ele
On 09-Oct-12 13:43, Marco Peretti wrote:
> light.exe : error LGHT0001: The filename, directory name, or volume
> label syntax is incorrect. (Exception from HRESULT: 0x8007007B)
> [C:\a\src\LockIt\MMC.Setup\MMC.Setup.wixproj]
Try getting a verbose log so you can see the stack trace.
--
sig://boB
h
On 09-Oct-12 14:23, Brian_Covington wrote:
> private void PlanPackageBegin(object sender, PlanPackageBeginEventArgs e)
Please file a bug on this -- I'd vote that it's a bug that the engine
doesn't call OnPlanMsiFeature; if it would and a feature state was
change, it would set the package action t
On 08-Oct-12 04:47, Daniel Bruce wrote:
> Our problem is not in specifying the packages (though thank you for that),
> but getting them to run prior to the .NET 4.0 package in the native installer
> that is launched if .NET 4.0 is not present on the machine. We think this
> would require setting
Okay, done. https://sourceforge.net/p/wix/bugs/3116/ LaunchAction.Modify on
Present package does not call PlanMsiFeature
From: Bob Arnson
To: wix-users@lists.sourceforge.net
Sent: Tuesday, October 9, 2012 10:00 PM
Subject: Re: [WiX-users] Detecting Feature
27 matches
Mail list logo
