Hi Team,
My MSI creates a virtual directory under a default website and creates a new
web application under existing App pool(this case DefaultAppPool). Which is
working fine on windows 2003 OS.
When I install the same MSI using Microsoft Octopus from Win7 onto windows 2003
server the installe
We have a WiX project in our VS 2008 solution. I would like to save the
project's build output to a file like BuildLog. Any ideas?
Regards,
Demyn
--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is th
Hi,
I localized all strings used in my installer UI. The installer is a MUI based
msi which means the same MSI can work on different locale machines and shows
the strings in the corresponding locale.
All dialogs works fine except that the launching page (the verify first dialog
showing somethi
On Tue, 15 Sep 2009 19:59:35 +, Lian Jiang wrote:
Lian,
You probably mean the very first small message about the installation
launching. This is displayed by the Windows Installer, not your installer. So,
no matter how fully you have localized yours, this message will display in the
actual
I've not come across the Vista scripting issue that Blair mentioned, but AV
programs are always looking for scripts that might be dangerous. In some cases
I believe they even intercept calls to the scripting engines. This is typically
the reason so many setups ask you to disable AV programs befo
By changing it to 'Order="3"' seems to be working. Thanks for the hint.
dl
Pally Sandher wrote:
>
> I'd try changing
>
> Value="UserRegistrationDlg" Order="2">LicenseAccepted = "1"
>
> To 'Order="1"' as from looking at the WiX v3.0 sources, WiXUI_Mondo.wxs
> has the following:
>
> Value="S
>From time to time I am getting the following dialog during install that never
>disappears and prevents installation from continuing:
Please wait while installer finishes determining your disk space requirements.
If I cancel the install and then restart it again m
I find it weird that the WI would reject VBS but accept a C/C++ dll?
There is nothing stopping someone from writing dodgy code in C/C++ and
shipping it with an installer.
Just because it is compiled it's safer?
Out software should be installed by Administrators, so I'm hoping they
will allow our
First thing I see is a component rule violation: C1 and C2 have the same
keypath (assuming both components are in the same directory). File F1 should
be installed by one and only one component (same with every other resource).
You will need to fix that somehow, since violations of the component ru
You will need to calculate/retrieve INSTALLDIR via a custom action you run
before AppSearch, or use some directory other than INSTALLDIR for our
EXE_EXISTS property.
Since you only run that EXE when it was previously present, is that EXE
placed there using a previous installer package? Could you u
Make sure it is before LaunchConditions and after AppSearch (you can move
either one of those if needed)
For example:
The usual caveat about VBS (or any other) script CA goes here: they are
unreliable (there are anti-virus systems that prevent the script from
running and, esp. on
Hi thanks Pally
I confirm the C1 and C2 file IDs are all different (I missed that in my example
for C2)
--- On Tue, 9/15/09, Pally Sandher wrote:
From: Pally Sandher
Subject: Re: [WiX-users] Component installed even if not part of selected
feature
To: "General discussion for Windows Installe
http://www.wixwiki.com/index.php?title=Deploying_Additional_Components might be
helpful.
-Original Message-
From: Muthuramakrishnan [mailto:s...@srasys.co.in]
Sent: Tuesday, September 15, 2009 5:07 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Rega
In that case are you bootstrapping the Windows Installer 4.5
redistributable before your installer runs so all your users/customers
will be able to successfully install your product or are you also
testing it on 3.1 & 4.0 to make sure they don't have problems?
According to the docs
(http://wix.sou
Give both app.exe unique File Id's & I suspect the shortcuts won't appear.
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. Regi
Hi,
I have something like
...
...
...
...
...
I select "Full" feature for installation; I know it's correct because C3
component files are installed. But I also get the shortcuts from C1 component
cre
I'm using v4.5.6001.22159 if that is any help to anyone.
Is putting my CustomAction before LaunchConditions the best place to run
my vbs, or would there be another more appropriate place?
Dominique.
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: 15 Septemb
Bob,
Sorry to trouble you.
Our tests show different behaviours of this dialog when installing from
local disk or CD room.
Our installer of single MSI file is about 400MB. When installing from CD on
a low spec machine, this "Preparing to install" dialog box is displayed
immediately, then OS hang
Hi,
Thanks for your reply, but i have to merge that bootstrapper with my
installer written by WIX.
Please let me know, any thing wich will help me!
Thanks
S.Muthuramakrishnan.
- Original Message -
From: "Pally Sandher"
To: "General discussion for Windows Installer XML toolset."
Sen
Looks like a problem with your bootstrapper. Try running it in a debug
session.
It shouldn't be affecting your installer though. Once msiexec has been
called to run your MSI your bootstrapper *should* have nothing more to
do with the whole process.
Palbinder Sandher
Software Deployment & IT Admi
I'd try changing
LicenseAccepted = "1"
To 'Order="1"' as from looking at the WiX v3.0 sources, WiXUI_Mondo.wxs has the
following:
LicenseAccepted = "1"
So it they could be conflicting.
Your code looks absolutely fine, other than this nothing jumps out as a
possible cause here.
If this fixes
hi All,
i've a sample installer which will be called by my setup.exe, while
launching setup.exe after welcome dialog suddenly installation was failing,
even logs doesn't giving any errors, so went to the event viewer and i found
one error. the error is like this:
Faulting application setup.exe, v
No but you could attribute it to a bug in whichever version of Windows
Installer you're using to test the MSI (v3.1 or v4.0 whether you're on
XP/2k3 or Vista/2k8 respectively I'm guessing).
People on this list really need to learn the difference between WiX &
Windows Installer. They are *not* the
Hi Blair,
Can we attribute this to a bug in WiX 3.0 then?
If I need to write a work around, does WiX provide any parsing
capabilities, or should I look at using VBScript or similar to get this
working?
Dominique.
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: 14 Septemb
Hi Blair,
Thank you for your help. I checked the log file. AppSearch(property
EXE_EXISTS) was set before INSTALLDIR but CA_RunEXE was called after INSTALLDIR
set.
Execute Sequences:
1. AppSearch property EXE_EXISTS assigned
2. Property INSTALLDIR assigned
2. CA_RunEXE custom action
25 matches
Mail list logo
