Hello All,
Our installer is built using Wix3. When I am running our installer I am seeing
that while the custom action code is still running MSI gets notified of the
error, rolls back and ends. The custom action code continues to run after this
point and completes without any problem.
I have de
I played with SharpSetup for an hour. I see some value, especially getting
started, but these neatly integrated things often end up being more of a drag
and time saved upfront has a very long tail.
I think it's an interesting idea that the Wix GUI editor is actually a form
editor that uses c# c
I've also released IsWiX on Codeplex ( http://iswix.codeplex.com ) It's
still in it's infancy but I can say we've used it at my day job for the last 9
months by about 20 developers and it's working really well for our
needs.Currently we use it for the heavy lifting of defining merge
modu
Hmm... it seems the PrintEula.dll functions are not called at all under this
virtualized Vista x64! If I hit the "Print" button in the EULA dialog, the
cursor blinks and then nothing! Still, I'm just guessing here...
The log:
Doing action: WixUIPrintEula
...
Invoke remote custom action
Hi there,
If I have a defered quiet CA:
If I want to have the rollback CA for the above, is there any way of doing
that? Because the property setting CA cannot be deferred but inmediate, so
changing to the below won't work:
thanks
Andres
No, the error lies in WiX!
Google only gives you a couple of hits - implying that this error does not come
from some Microsoft component.
>From WixUI_en-us.wxl:
Installation directory must be
on a local hard drive.
Also tried this:
msiexec /i MySetup.msi WIXUI_DONTVALIDATEPATH="1"
I modified PrintEula.dll to not use the PathIs* APIs, but it kept failing. In
the Wix sources I can see the following:
1
No matter what's causing it, it has disastrous implications. Not being able to
install my software on virtual machines is simply not an option :(.
> Date: Thu, 1
If you Google that error it seems select people hit it even on real physical
boxes, under other flavors of Windows (98, XP), too. Windows misreporting the
drive type if I had to guess. Probably nothing wrong with your authoring. I'm
not seeing any definitive solutions out there.
-Original
Hi,
Using Wix 3.5.
Tried my new MSI under Vista Home Premium, emulated under VMWare 7. It gives me
this obscure error when I hit "Next" in the "Destination Folder"-dialog (simple
WIX UI):
"Installation directory must be on local hard drive."
Reading the logs:
Doing action: WixU
I was just getting ready to start a new WiX project except it was
looking like I would have to do a lot of custom GUI, then I came across
this http://sharpsetup.eu/
-Michael Clark
--
__
Hi,
I created two patchs and I tested both and they are working.
But when I install both together an error occurs.
How Do I solve this problem?
I want to install a lot of patchs in the target setup.
How Do I do?
Patch One:
http://schemas.microsoft.com/wix/2006/wi";>
http://www.con
It doesn't seem to me that you need code for any of this. These are all type 51
custom actions that set a property to true or false conditioned on some other
property. You could declare all these as properties with a default value of
false and have type 51-s to set them true. Managed code seems
It's in the docs for the DoAction ControlEvent:
http://msdn.microsoft.com/en-us/library/aa368322(VS.85).aspx
which is what custom actions called by a pushbutton are.
"Note that custom actions launched by a DoAction ControlEvent ...
cannot send a message with MsiProcessMessage."
Hi,
That is not entirely correct. When you reference one project to another,
msbuild doesn't copy anything. It simply makes the reference project available
to the target project. It is up to the target project itself to decide what
it's going to do with that reference. In the case of a c# pr
The ExecuteMode switch also helps a lot.
msiexec /I MySetup.msi /l*v log.txt ExecuteMode="None"
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Thursday, May 13, 2010 9:10 AM
To: General discussion for Windows Installer XML toolset.
Subject:
msiexec /I MySetup.msi /l*v log.txt
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail
> -Original Message-
> From: Kristoffer Danielsson [mailto:
Hello!
I have WiX project included into Visual Studio solution along with
other projects written on C#. In order to automate build process I
need to get output files from some of C# projects, and add them to
.msi file.
Usually when you add reference from one C# project to another,
msbuild copy f
Also a good idea :)
msiexec MySetup.msi /L*v > log.txt
Right?
> Date: Thu, 13 May 2010 10:22:36 +0100
> From: pally.sand...@iesve.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Files not removed upon uninstallation
>
> And check verbose logs when you run into probl
Ah, great idea! Thanks!
> From: phil.wil...@invensys.com
> To: wix-users@lists.sourceforge.net
> Date: Wed, 12 May 2010 18:54:44 -0400
> Subject: Re: [WiX-users] Files not removed upon uninstallation
>
> Use a virtual machine and revert back after your install/uninstall tests!
>
> Phil Wilson
You can't, you need a bootstrapper.
http://dotnetinstaller.codeplex.com has native support for MSUs.
Cheers
dB.
dB. @ dblock.org
Moscow|Geneva|Seattle|New York
-Original Message-
From: Sajo Jacob [mailto:spja...@gmail.com]
Sent: Thursday, May 13, 2010 10:13 AM
To: General discussion
Couple of questions here:
1) My installer is basically a machine prep install which needs to update
the target machine with an msu. How can I chain an MSU with WiX?
2) I need to turn off "Windows Update Service" as the last step in my
installer, but the MSU update can restart the machine so how c
I hope this is correct.
1) The Valid_Samples is my Custom action name in the wix code
2)I have set the Property for the Custom action and set some values for
intially
3)I have called the Custom action in the Dialog next button.
1
Please let m
I did. So it means that unless I change the installer to current user I have
to somehow dynamically obtain the path of the current user desktop?
On Thu, May 13, 2010 at 7:16 PM, Pally Sandher [via Windows Installer XML
(WiX) toolset]
> wrote:
> Read the MSDN page I linked.
>
> Palbinder Sand
Read the MSDN page I linked.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
Registered Off
Pally, do you happen to have a code sample? Or do you mean it is near
impossible?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Desktop-Shortcut-on-Current-User-Only-tp5044866p5045433.html
Sent from the wix-users mailing list archive at Nabble.com
1 - I don't know. Modify your bootstrapper code so it launches your
MSI's with /lvx* ? Maybe search Microsoft support site & find
this http://support.microsoft.com/kb/223300 ? It's only the first result
in Google when I typed "Windows Installer logging" into the search
field.
2 - Read what I asked
1) I can't able to check the verbose log. Because we are generating the MSI
and use some bootstrapper for prerequisites and then generated the exe. How
we can generate the LOg for the exe ?
2) This is my custom action code.
using System;
using System.Collections.Generic;
using System.Text;
using
1 - Check a verbose log.
2 - Post your Custom Action WiX code. Half the code sample isn't much
help.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmenta
BTW Chad is correct, you can't have a single MSI that targets x86 & x64
locations on the system, it's an either/or situation.
x86 MSI's on x64 systems will be redirected to the x86 directories &
registry locations by WOW64, x64 MSI's can't be run on x86 systems.
MSI's must have a single platform sp
Hi,
Can you please send the link that contains the samples for Burn. Can we
eliminate the Bootstrapped for installing the prerequisties like SQLCE after
the product installtion by using Burn.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-sam
Hi
Whille installing my setup When i click the Next button in the Dialog i got
the following error
"There is a problem with this Windows Installer package. A DLL required for
this install to complete could not be run. Contact your support personnel or
package vendor. "
In Next Button i have the
And check verbose logs when you run into problems. In my experience 95% of the
time it'll tell you what you're doing wrong or at least point you in the right
direction.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.c
http://msdn.microsoft.com/en-us/library/aa368276.aspx
Not possible without some serious custom coding.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmen
Also note that I have a property as follows in my installer:
This means the installers is set so that it installs on all users I guess. I
am not at liberty to change this - I only need to create a DesktopShortcut
on current user while the setup installs on all users.
--
View this message in co
34 matches
Mail list logo
