The problem is the Package/@Compressed attribute, you have this set to
no so that file are placed uncompressed in the same location as the
MSI not embedded into the FEMedia.cab as specified by the media element.
So the warning is correct in that there aren't any files in the cab
file. If you
Dear Friends,
It seems that in WiX 3, the TARGETDIR is set to the local drive which has
the most free space on the system.
I need to hardcode this so the user will always see C:\MyProgram\ as the
default install path.
For this, I've done the following:
Property Id='TARGETDIR' Value='C:\'/
I will be out of the office starting 04/25/2009 and will not return until
05/03/2009.
I am attending a training course off site. I will respond to your message
when I return.
--
Crystal Reports #45; New Free Runtime
Hi,
Does Windows Installer allow to remove all the files authored within a
component by applying a patch?
For example a patch (small update) would like to remove both files from the
next component:
Component Id=Comp_1 Guid=884C0AD3-4249-41d5-A722-60007DC9402B
File
Hi,
I am building a patch (with the torch,pyro method and a separate wxs file
that describes Patch and PatchFamily elements) for removing some files from
the installation folder and some additional modifications in the existing
files. Therefore, I have to use the element RemoveFile. Until now
Hi All,
I'm a novice to WIX would like to know 'Is it possible to create an exe
out of exe's using wix ?
i.e. I need to create a one click installer out of the available exe's where
in running the primary exe installs all the secondary exe's in a sequence.
Can this be possible using the wix, if
Thank you for the solution.
Now I am using the 'QtExec' but when i make the .msi and run it then it's
ending prematurely.
here is the code snippet i am using:
Property Id=RUNBATC:\Program Files\APP\run.bat/Property
CustomAction Id=RUNBAT BinaryKey=WixCA DllEntry=CAQuietExec
Return=check
Hi Riyaz, not exactly sure why you want to hard code it to the C:\ folder?
Take a look at this as it might be what you want to do:
http://www.dalun.com/wix/04.25.2007.htm
Also you can do this:
http://n2.nabble.com/How-to-Change-Default-Install-Location-td1092961.html
I haven't noticed that wix
Hukum, I would try immediate Execute=immediate Also I would log the
install to see if you can find the problem(see below)
Other than that, I second what Brian said below as well as Rob has said
many times, dont use batch files in your installer, you are asking for
problems.
From wix help:
When
Hi Thank you for reply,
I got following error in the log file.
MSI (s) (98:A8) [17:55:01:125]: Doing action: CHANGEREGBAT
MSI (s) (98:A8) [17:55:01:125]: Note: 1: 2205 2: 3: ActionText
Action 17:55:01: CHANGEREGBAT.
Action start 17:55:01: CHANGEREGBAT.
MSI (s) (98:A8) [17:55:01:265]: Creating
Just worse after I see what your batch files says changeregbat. if you are
changing registry entries you can do it through wix very simply plus you get
the rollback.
http://wix.sourceforge.net/manual-wix3/write_a_registry_entry.htm
If you want to do alot of registry entries based on multiple
There's no harm, it just violates a strong suggestion.
On Sat, 25 Apr 2009 12:29 +0430, Riyaz Mogharabin
moghara...@gmail.com wrote:
Dear Friends,
It seems that in WiX 3, the TARGETDIR is set to the local drive which has
the most free space on the system.
I need to hardcode this so the
spsingam wrote:
it would be nice to be able to use the msiexec /a and get the
Administrative install to work.
how would large organisations deploy msi/s if they cannot push it out via
group policy.
That doesn't require UI. As I indicated last year, admin UI dialogs are
rarely requested
Pally Sandher wrote:
Unfortunately the WiX extensions solution is in Visual Studio 2008
format as we're still using Visual Studio 2005, I can't rebuild
WixUIExtension.dll to test changes even if I wanted to help update them
myself.
WiX can be built with all no-cost tools and VS supports
Shawn Dwyer wrote:
Is there anything I can do at this point to prevent our (already released)
2.x from installing over our (in development) 3.x?
That would require time travel, so probably not. Your 2.x product is
related to your 3.x product only via the upgrade code and MSI explicitly
Dale Quigg wrote:
Running a verbose log during upgrade shows that FindRelatedProducts is
working.
What's logged for MigrateFeatureStates?
--
sig://boB
http://joyofsetup.com/
--
Crystal Reports #45; New Free
Karthik Krishnan wrote:
It is buried/implied in the documentation, but there is a simpler way. Just
change the sequencing of the windows.
That is not a reliable method. See
https://sourceforge.net/tracker/?func=detailatid=642714aid=2780533group_id=105970.
--
sig://boB
http://joyofsetup.com/
slmnow wrote:
So how can i differentiate between the user doing msiexec /passive /x
{xxx-xxx} vs a normal uninstall.
You can't. There's no difference between how ARP runs your uninstall and
how someone might run it programmatically or via the command line.
--
sig://boB
barry wrote:
anyone know how adding a bootstrapper could cause comboboxes to freeze on a
custom ui dialog?
You probably want to talk to the bootstrapper folks.
--
sig://boB
http://joyofsetup.com/
--
Crystal
Rajesh Chintamani wrote:
I'm a novice to WIX would like to know 'Is it possible to create an exe
out of exe's using wix ?
No. WiX is a toolset for building Windows Installer packages.
--
sig://boB
http://joyofsetup.com/
Christopher Karper wrote:
5.) I build the Installer project using the WixExtension... I get a candle
error candle.exe(0,0): error CNDL0144: The extension
'..\..\..\Install\WixExtension\WixExtension\bin\Release\WixExtension.dll'
could not be loaded.
Use fuslogvw to see why binding failed.
Generally you should not remove files in a patch, but if you must: within
the same component that owns the files remove the File elements and add
RemoveFile elements for the same files. You cannot, however, remove the
KeyPath file legally. You also cannot remove the component or you will break
any
What you did is recommended for removing non-keypath files. Please post your
entire verbose patch installation log.
On Sat, Apr 25, 2009 at 2:37 AM, luciana istoc istoc_luci...@yahoo.comwrote:
Hi,
I am building a patch (with the torch,pyro method and a separate wxs
file that describes Patch
This is not a recommended use for patches. If you're going to update all
files, you should consider a major upgrade instead.
To avoid the issue where the patch always sequences to the highest
ProductVersion (which means you must change the ProductCode or some other
identity property, or you lose
The components were not removed because another product (or product version
installed side-by-side) installed them. Removing the files does not
unregister the products. You need to identify which other products installed
those components and uninstall those products (or at least uninstall the
Thanks for the information. I'll look into using a major upgrade instead of
the way I'm currently doing it. The only real requirement is that the install
be as lightweight as possible. The initial install MSI is 15 meg due to the
Visual Studio runtime and when I update the exe I don't want
You might want to look at adding the entire namespace as -ext
My.Test.Namespace.WixExtension and put the extension in the root with
candle.
Brian Rogers
Intelligence removes complexity. - Me
http://icumove.spaces.live.com
On Sat, Apr 25, 2009 at 8:32 AM, Bob Arnson b...@joyofsetup.com wrote:
I was under the impression that's what the EmbedCab attribute does. That
mostly makes sense. Thanks for the explanation.
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Saturday, April 25, 2009 2:56 AM
To: General discussion for Windows Installer XML
Thanks for the reply.
Now somehow I am able to suppress the dos window. But now I am stuck at some
different problem.
code snippet is:
CustomAction Id=SETRUNBATCH Property=RUNBATCH
Value=quot;[RUNBAT]quot; quot;[DEFAULTINSTALLLOC]quot;
quot;[JAREXE]quot; /
CustomAction Id=RUNBATCH
29 matches
Mail list logo
