Can we remove this cancel button or is it
mandatory to retain it for the windows logo compliance of the application?
*where can i find the related info?* any help?
Perhaps the MsiUiHideCancel property might be a trail towards what you
would like to achieve:
Something that might come handy:
The package can be also deployed as a per machine installation, and after
that it will be out of the scope of the users to tamper with the installed
state of the software, but they'll still be able to launch it.
2007/11/30, Huseyin Tufekcilerli [EMAIL PROTECTED]:
Let's assume the file has been successfully replaced by the new version.
Should that new version be later uninstalled together with the package which
overwritten it?
2007/11/29, Szentpali Janos [EMAIL PROTECTED]:
I have an executable x.exe that I need to install over x.exe if it
already
Sure, MSI should have the ability to combine complete MSI installation
packages as phases of the installation, together with the transactional
behaviour (including savepoints on the registry..)... is this
something related to staged installation Windows Installer 4.5?
Otherwise there might be
Wouldn't a true solution be writing a chainer (bootstrapper)?
Otherwise I agree with Christopher: these why do you think answers are
implications of something that lies in the philosophy and the state of
art - if the developer is assigned to preparing the installation, the
developer thinks like a
If removal is what you expect, ICE validation (either with Orca or smoke) is
related to the question, and running it will help you in case roaming user
profiles would be involved.
As I remember Registry... values are removed together with the contents of
the component they belong to.
2007/11/14,
Nope, I was wrong.
See the action attribute of registry element in the WiX help.
2007/11/14, János Brezniczky [EMAIL PROTECTED]:
If removal is what you expect, ICE validation (either with Orca or smoke)
is related to the question, and running it will help you in case roaming
user profiles
Probably. Perhaps the cost is the result of the things mentioned at
http://en.wikipedia.org/wiki/Windows_installer, in the Disadvantages/Large
footprint section at the bottom of the article.
2007/11/5, Brian Simoneau [EMAIL PROTECTED]:
There are multiple features, and some of them are hidden,
with MsgBox), and so on.
It still has no effect, while changing the property value in the property
element works appropriately.
Why?
2007/10/27, János Brezniczky [EMAIL PROTECTED]:
First of all, thank you for answering.. my problem is that the checkboxsticks
to the value provided long before
Hi all!
I'm using WiX 2.0.5325.
I'm trying to initialize a checkbox control which is linked to a property.
The property is initialized according to different conditions which are
evaluated by a vbscript customaction, far before the dialog containing the
control shows up. In fact I even tried
First of all, thank you for answering.. my problem is that the checkbox
sticks to the value provided long before the script runs, no matter what
value I provide, and if I don't specify one, it remains unchecked because of
the default 'empty' value of the property. It seems to be immune to whatever
If it is related to some UI things, an adequate UiRef element could help you
to include it clearly.
2007/10/26, Karim MacDonald [EMAIL PROTECTED]:
Hello,
This may be a misunderstanding of how WiX is supposed to work.
Basically...
I have a Fragment file, InstallExecuteSequence.wxs, that
The commonly accepted solution is breaking up the code into fragments. The
source code of WiX UI (wixui.wixlib) might be of your interest, as it is a
good example (I think, what I write at least stands for WiX 2.x).
In this case, for each level of UI - depending on how far it is reduced
-
You can e.g. replace the license.rtf file found in the wix binaries
directory, but that would be a bit rude solution. I think otherwise the file
should be placed in the folder with the .wixobj files to be built with
light.
I hope someone corrects me if I'm wrong.
2007/10/17, Levon Levonian
Sounds evident, if I'm not wrong... the answer is in your letter.
Have you tried sequencing it with installexecutesequence (and
adminexecutesequence)?
I mean adding
InstallExecuteSequence
StartServices Sequence=enter_a_sequence_number_big_enough_here /
/InstallExecuteSequence
It should work as
It should be included in the downloaded WiX package... In case of WiX2 it is
in the root folder of the zip file.
2007/10/5, V K Gangwar [EMAIL PROTECTED]:
Hello All,
How I can get wixca.dll.
regards,
Veerendra
--
Take the Internet to Go: Yahoo!Go puts the
2007/9/26, Chris Ridd [EMAIL PROTECTED]:
On 25 Sep 2007, at 23:39, János Brezniczky wrote:
I would just add that it's easier to set Compressed=yes on the
Package instead of setting it on each individual File element. (I
use WiX 2)
But does it also apply to merged in modules? We're
Peter,
I've just upgraded the Win2k3 Server to SP2, and there was something I
missed to notice yesterday.
First of all yesterday I thought the Windows Installer service might not
have had the required privileges, so I simply tried to change the
account under which the service was run to
Hi,
I would try incrementally adding these files to see which ones cause the
collision. Seems to be a problem with duplicate identifiers. Otherwise merge
modules should work .. however merge modules are originally indended to ease
the deploying of 3rd party products' installers and allow to
Perhaps
http://msdn2.microsoft.com/en-us/library/aa368043.aspx
I was a little surprised when I came upon the following sentence in the WiX
2 help:
*Note: This document assumes you have a working knowledge of the Windows
Installer database format.*
**
I had been using/trying to use WiX for at
I think you should try manually registering the dll from an administrative
prompt.. there might be a problem with execution rights. (?)
2007/9/25, Craig0ss [EMAIL PROTECTED]:
no registering the dll manualy fails as well, im not sure if its a vista
prob as it works fine on XP
Strele
I would just add that it's easier to set Compressed=yes on the Package
instead of setting it on each individual File element. (I use WiX 2)
2007/9/25, Chad Petersen [EMAIL PROTECTED]:
For each File element I also had to use the Compressed=yes attribute.
Using WiX 2.0.5325.0. Older versions
Hi,
According to this topic I'd like to ask whether it is a good or bad choice
if I use an embedded DLL (Binary) implenting the functionality to tackle
with the running executable issue. It becomes interesting when it comes to
deploying the application to 64 bit platforms. I mean in this case,
Thanks for the answer! I've been a little late with trying, but anyhow
redundant be the code ... it works! :)
2007/9/13, Mailinglist [EMAIL PROTECTED]:
Well, I do have the same problem, specially when it comes to votive.
The files must be duplicate, to be used in two projects, linking to
I don't know if it helps, but you could try specifying a Name property for
the program menu folder. I'm not familiar with WiX 3.x, but it worths a try.
2007/9/15, Debbie Highgate [EMAIL PROTECTED]:
Hi,
I have a file that I've modified from a (working) WiX 2.0 file.
light.execomplains about
Perhaps you could use a VBScript customaction to determine which value is to
be set according to the values read from the registry before. (From VBScript
the properties can be read/set by using *Session.Property(PROPNAME)* )
2007/9/13, rbok78 [EMAIL PROTECTED]:
Hi,
I would like to install
Hi,
What documentation do you mention? I couldn't manage to find the
Publish.Dialog attribute, but I would also be interested in this method of
overriding the default event linking between dialogs. (Thanks for a link if
appropriate.)
Otherwise I suppose these Publish nodes should be parented by
Hi all,
I just would like to know under what conditions does the following action
execute:
CustomAction Id='AlreadyUpdated' Error='Foobar 1.0 has already been updated
to 1.0.1 or newer.' /
(The snippet is taken from the WiX Tutorial, lesson 4: *
, Rob Hamflett [EMAIL PROTECTED]:
It's explained immediately below that piece of text. During the
InstallExecuteSequence, after
FindRelatedProducts if PATCHFOUND is set. PATHCFOUND is set (or not) in
the Upgrade table, which is
detailed in the preceding few paragraphs.
Rob
János
I guess my problem is very similar, i.e. includes the one mentioned above...
I'm struggling with a forthcoming a product which has three optional
components. It is OK to have a single installation containing these as
different features. In reality we should obtain packages combining
these three
30 matches
Mail list logo
