Hi,
Iam creating an MSI for Windows7 64 bit and Windows 2008 r2..Iam running
that Msi as run as administrator through command prompt.
My problem is when iam changing the drive through WixUIInstallDir.its not
changing the drive where i want..
it is checking the drive which is having
You could make the Perl feature a child of the Java feature. It might
look a little strange on the Feature selection tree, but it should work.
Rob
On 04/02/2013 09:34, Tal Maoz wrote:
Hello all,
I'm trying to add a feature dependency into an installer and I can't find
how to do this.
here
Have you seen this page ?
http://msdn.microsoft.com/en-gb/library/windows/desktop/aa371614%28v=vs.85%29
.aspx
Scroll down to INSTALLMESSAGE_FILESINUSE
The files in use error message is in the MSI's Error table (error 1603) and
could be changed with a wix Error element.
I'm not sure how the 2 tie
Hi,
I did some testing and it looks like you can control which shortcuts appear
on the main start menu with shortcut properties, otherwise windows will
decide on its own which appear on the main menu.
System.AppUserModel.StartPinOption
Greetings.
I have run into a scenario where I want to disable the ability to run a Change
install from Add/Remove Programs and the MaintenanceTypeDlg after all available
Features have been installed. This works fine if all Features are selected
during the initial install but if a single
DCIM should be on the path so adding C:\Windows\system32 shouldn't be necessary.
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: 04 February 2013 22:09
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn: Prerequisites
This is really useful information. Thank you.
Just to be clear is the first property actually required to hide the shortcut?
E.g.:
ShortcutProperty Key=System.AppUserModel.ID
Value=Company.TheApplication.exe /
Neil
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent:
Ignore me, I didn't read the comment properly!
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: 05 February 2013 20:32
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Win 8 Tile from wix
This is really useful information.
For me, running dism.exe only worked if I put in the full path. Not sure
why that is.
Eric
On Tue, Feb 5, 2013 at 2:22 PM, Neil Sleightholm n...@x2systems.com wrote:
DCIM should be on the path so adding C:\Windows\system32 shouldn't be
necessary.
-Original Message-
From: Hoover,
I think that is probably related to burn being 32 bit and dcim running from 64
bit system folder so the current environment is not passed to the process. May
be the code could support expansion of a [SystemFolder64] property.
Neil
-Original Message-
From: Eric Schultz
It's acceptable to include the same components (your Java components) in two
different features.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-feature-dependency-tp7583348p7583384.html
Sent from the wix-users mailing list archive at
It is MSI's default behavior to choose the disk with the most space. Try
capitalizing the property to TARGETDIR.
TARGETDIR=E:\
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Msi-is-not-creating-in-the-Drive-tp7583373p7583385.html
Sent from the
here i dont want to give the 'TARGETDIR' through command.when i click on the
'WixUIDir' it should select the drive and have to go..
how to do.
-Original Message-
From: Nick Ramirez [mailto:nickra...@hotmail.com]
Sent: 06 February 2013 05:23
To: wix-users@lists.sourceforge.net
Subject:
13 matches
Mail list logo