Man, Shirley wrote:
The workaround is, before launching installer, manually remove the
folder with files that have been installed with previous installation.
Here is the verbose log of the second install attempt. Notice there is
a 38 second hang at the line :
MSI (c) (44:78) [16:43:58:779]:
Mike Dimmick wrote:
> Doesn't a patch effectively turn into a minor upgrade, or have I
> misunderstood this?
>
Generally, patches are run from a bootstrapper to get a better UI
experience but it's possible to use them as a double-clickable minor
upgrade, yes. Minor upgrades are just new packa
Frédéric Viollet wrote:
> Ok.Thanks. Is there a documentation somewhere on how to use the
> setupexe bootstrapper?
Not really, no. Here's the command line I use to build one:
"%WIX%\setupbld" -out "%DIR%\foo.exe" -mcsp "%DIR%\foo.msi" -setup
"%WIX%\setup.exe"
> Value="ChoosePortDlg">1
> to m
Please keep /wix-users/ on the thread.
Hao Liu wrote:
When I run the msiexec 4.0 on vista to install the msi, I found the
process running as a medium-level process instead of high-level
process, and I even could not create application folder under
C:\Program Files, and also it did not have p
Scott Sam wrote:
So I did the sn -Vr *,36e4ce08b8ecfb17 thing, then I built wix using
the make.bat file. I still couldn't just throw in the files that I
had changed, so I uninstalled WiX and reinstalled it using the
wix3.msi file created when I built wix. That worked on the machine I
had b
Ian Stevenson wrote:
I see you've already gone down the exe path somewhat, but I would like
to point out that you can debug MSI DLLs - just not via the debugger
(albeit maybe you can, as the links below made mention of info in
MSI.chm, but I believe it is meant to be a lot of effort).
It's no
Hi all,
Has anyone seen this Windows Installer behavior before?
1) Launch installer, proceed to Copying Files stage.
2) Reboot computer in the middle of copying files
3) Relaunch installer again.
4) Installer will freeze for awhile in the EULA screen (and sometimes it
freezes to death).
The wo
I see you've already gone down the exe path somewhat, but I would like
to point out that you can debug MSI DLLs - just not via the debugger
(albeit maybe you can, as the links below made mention of info in
MSI.chm, but I believe it is meant to be a lot of effort). You need to
rely on other debuggin
I think I will use Binarykey as this file is only needed at install time which
generates an unique license file. After that the purpose is nill for this file.
Srini
But how should I call an exe with arguments?. Any Idea.
I serached on web and could not find proper documents.
Pl
But how should I call an exe with arguments?. Any Idea.
I serached on web and could not find proper documents.
Please anybody know help.
Srini
"Pierson Lee (Volt)" <[EMAIL PROTECTED]> wrote:
v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);}
w\:* {beh
Binary Key -> takes a tag with a dll/exe and will run it without
extracting/installing it (the Binary is only valid at installtime)
File key -> an extracted file that you need to access at install time also.
This file will also be available after installation as per your tag.
From: [EMAIL PROT
I really fed up working with .dll as there is no debug available. Now I created
an .exe with the same code.
From the command line the usage is as folows:
write.lic.exe 61177-1128925439-1187326800 9.0
I need to pass the CD-Label key in the first argument and the version as
second ar
Doesn't a patch effectively turn into a minor upgrade, or have I
misunderstood this?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: 17 July 2007 15:42
To: Frédéric Viollet
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] minor
That's really not a very helpful message, is it?
Could you post the command line you passed to light? Does this always happen
with all installers or is this only happening with one? Does it still occur
with an older version of WiX? (e.g. 2.0.5213.0, available from
http://wix.sourceforge.net/releas
I followed the first example and I am not getting the value into a control.
Here is what I did:
My installation sequence:
I want to get the CDKEY value to test before actually running dll. However,
my control does not fill with CDKEY.
You have to use a bootstrapper, you don't have to write one. Take a
look at the GenerateBootstrapper task or dotNetInstaller or NSIS.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Tuesday, July 17, 2007 11:31 AM
To: wix-users@lists.sourceforge.net
Subje
I know this has been asked before, but is there still no way to launch
another installer from another.
Apparently, for msxml60, Microsoft has abandoned the merge module
approach and is only distributing an msi which they recommend you launch
silently from you current installer.
I would l
Hi everyone,
I've got a question about merge modules.
I've written a merge module and I would like the files of the merge
module to install themselves in the directory that the user selects
while installing the main package.
Example:
*Merge Module:
Program Files
My Product
bin
ApmFil
Microsoft (R) Windows Installer Xml Linker version 2.0.5325.0
Copyright (C) Microsoft Corporation 2003. All rights reserved.
light.exe : error LGHT0001 : Index was outside the bounds of the array.
Exception Type: System.IndexOutOfRangeException
Stack Trace:
at Microsoft.Tools.WindowsInstalle
thanks for the reply. I assume using a custom action to set a value of the
install directory is easy:)
Thanks again
Onur
On 7/17/07, Bob Arnson <[EMAIL PROTECTED]> wrote:
Onur Simsek wrote:
I am writing a plugin and I need help in getting an environment variable's
value and install my plugin
Bob Arnson a écrit :
Frédéric Viollet wrote:
Is there a way to perform a minor update without having to add on the
command line REINSTALL=ALL REINSTALLMODE=vomus ???
No. If you want to be able to double-click a package to get an
upgrade, it's got to be a major upgrade MSI package or a bootstr
You don't need to use square brackets in the condition because
properties are automatically resolved.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Craig Ward
Sent: Tuesday, July 17, 2007 9:24 AM
To: wix-users@lists.sourceforge.net
Subje
Craig Ward wrote:
> I have an InstallExecuteSequence block, within which I currently run
> actions depending on whether the installation is installing or removing.
> I'd like to extend the installing condition to include the Change/Repair
> modes that are available in the maintenance dialog.
>
Onur Simsek wrote:
I am writing a plugin and I need help in getting an environment
variable's value and install my plugin to that directory. My env.var
is % AppinstallDir%. This variable contains the full path of the
application.
So I am accessing to the value using *$(env.AppinstallDir
Frédéric Viollet wrote:
> Is there a way to perform a minor update without having to add on the
> command line REINSTALL=ALL REINSTALLMODE=vomus ???
No. If you want to be able to double-click a package to get an upgrade,
it's got to be a major upgrade MSI package or a bootstrapper .exe that
kno
Lawrence wrote:
>
> (&featureId)
>
>
> I get an error saying that a ';' was expected.
>
First, you need to compare the feature action state to some value. 3
means "being installed locally." Second, the ampersand is an special
character in XML; you can use
or
&featureId=3
--
sig://bo
Scott Palmer wrote:
> I've only used merge modules to install shared components like the VC8
> runtime. I assume that merge modules would update all products in the
> case of machine-wide shared components like that.
Patches target specific products so they can't be used to let Microsoft,
fo
Mailinglist wrote:
> Even if the directory changed by the user is overwritten, why are only the
> directorys of that one msm in user given path and all other files and dirs in
> the overwritten one. If the custom action overwrites the directory, it should
> overwrite it for all msm, shouldn' t i
Take a look at the Conditional Statement Syntax
http://msdn2.microsoft.com/en-us/library/aa368012.aspx
&featureId must be compared to a numeric value depending on what you are
trying to determine. For example, the feature would be set to install
if &featureId = 3, where 3 is INSTALLSTATE_LOCAL.
> I get the following error while running the .msi created by using the
> following code to create a service using WIX.GService.exe is the
> service exe
> file.I've copied installutillib.dll,GService.exe to the wix-binary
> folder(folder where candle.exe and light.exe exists)and created a
> service
On 7/16/07, Bob Arnson <[EMAIL PROTECTED]> wrote:
Scott Palmer wrote:
> Microsoft certainly doesn't like to make things easy do they? I
> assume though that if someone in the WMF group clued in to using MSI
> that they might also have the foresight to provide a merge module for
> the redistrib
I get the following error while running the .msi created by using the
following code to create a service using WIX.GService.exe is the service exe
file.I've copied installutillib.dll,GService.exe to the wix-binary
folder(folder where candle.exe and light.exe exists)and created a
service.xml file w
Thank you very much. Very good documents. Understood what needs to do. Thanks
again.
Ian Stevenson <[EMAIL PROTECTED]> wrote:
Hi Srini,
The idea is that you don't explicitly pass any arguments to the function call
(the only argument being the MSI handle that get's set by the i
I have an InstallExecuteSequence block, within which I currently run
actions depending on whether the installation is installing or removing.
I'd like to extend the installing condition to include the Change/Repair
modes that are available in the maintenance dialog.
I'm trying this but with no suc
Try giving the property name all capitals, i.e., MYPROPERTY.
Rennie
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Craig Ward
> Sent: 17. juli 2007 13:32
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] updating properties
>
> I'm
I'm trying to update a property from a PushButton. So, in my project
file I have:
MyDefaultValue
, and in a dialog I have:
1
1
Unfortunately, this doesn't change the property from its default
value.
Any ideas?
Microsoft (R) Windows Installer Xml Linker version 2.0.5325.0
Copyright (C) Microsoft Corporation 2003. All rights reserved.
light.exe : error LGHT0001 : Index was outside the bounds of the array.
Exception Type: System.IndexOutOfRangeException
Stack Trace:
at Microsoft.Tools.WindowsInstalle
Hi everyone,
I quite new to Wix and I'm using Wix V3. I've looked around for a
solution to my problem but I can't find anything maybe you will be
able to help me.
So here's the problem:
Is there a way to perform a minor update without having to add on the
command line REINSTALL=ALL REINST
Hello!
I`d like to know can I modify properties of the existing Default Web Site
using wix.
If I try
it will delete site when uninstall.
And if WebSite is not in the component than I cannot specify DirProperties
But I don`t n
Bob Arnson wrote:
>That looks fine but the sequencing you give in an earlier message means
>that any directory chosen by the user will be overwritten by your
>DirectorySet custom action. You want to add a condition -- NOT TARGETDIR
>-- so it doesn't run if the user has already specified one in the
40 matches
Mail list logo
