Hello,
I understand the docs are broken on the website (not the links but the
content). So I am curious what is the recommended way to view the
documentation? I downloaded the source and the only file in the doc
directory is example. Unfortunately I cannot build the source as I do
not have Windows
How to figure out what is the problem?
I am getting this in the compile:
-- Rebuild All started: Project: desktop, Configuration: Debug x86 --
C:\Program Files\Windows Installer XML v3.5\bin\candle.exe -v -dDebug
-d"DevEnvDir=C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\\"
In this case, using Before="InstallFinalize" will probably work.
Another option might be Execute="Immediate" and schedule
After="InstallFinalize".
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider
Custom Action MathPLay runs the Mathplayer.EXE from the design science
These can be installed anytime.. really it could be after all the files are
installed.
but i shall dig more into this , google probably
Vasu
On 4 November 2010 22:37, Castro, Edwin G. (Hillsboro) <
edwin.cas...@fiserv.com>
I think the WriteIIS7ConfigChanges custom action is not scheduled until run
time when windows installer is figuring out what to execute in the installation
transaction. The light doesn't know about it at link time so you get a failure.
Edwin G. Castro
Software Developer - Staff
Electronic Bankin
Current sources are all on Codeplex now. Anything still on SF is stale.
-Original Message-
From: Richard [mailto:legal...@xmission.com]
Sent: Thursday, November 04, 2010 9:22 AM
To: WiX Users
Subject: Re: [WiX-users] Documentation links are broken
In article ,
Rob Mensching writes:
What are you trying to do? Is SetWebLogFolderProperty a deferred action or
an immediate one? What is it doing in your transaction?
-Original Message-
From: Joe Osman [mailto:joe.os...@taitradio.com]
Sent: Wednesday, November 03, 2010 7:45 PM
To: 'General discussion for Windows Installer X
Notice that the following CustomAction elements all have an After attribute set
to InstallFinalize.
You'll need to choose an appropriate point in the InstallExecuteSequence
between InstallInitialize and InstallFinalize.
Then you can use the After or Before attribute to specify when to run them.
I
Awesome except that burn isn't actually fully baked yet.
Either way, I can tell you from my Continental Airlines days that caching isn't
enough because you'll always have users and administrators who intentionally
whack the cache to free up disk space. Tools such as SMS 2003 ( I have never
I want to schedule a custom action to execute after
WriteIIS7ConfigChanges but my build fails and I get the following error:
Error177Unresolved reference to symbol
'WixAction:InstallExecuteSequence/WriteIIS7ConfigChanges' in section
'Product:*'.
Here is the code:
NOT Installed AND NOT
So assuming that I am a newby in this, please could you tell me what i need
to change in the code?
Thanks
Vasu
On 4 November 2010 16:56, Castro, Edwin G. (Hillsboro) <
edwin.cas...@fiserv.com> wrote:
> The error tells you exactly what you are doing wrong. It says you must
> schedule the custom ac
Very true. That's why Burn caches the MSI for you.
Minimizing source prompts is good as well...
On Thu, Nov 4, 2010 at 12:25 PM, Wilson, Phil wrote:
> I've also seen this behavior during upgrades. The source MSI always need to
> be available, whether we like it or not, because you can't tell wh
I've also seen this behavior during upgrades. The source MSI always need to be
available, whether we like it or not, because you can't tell when this can
happen.
A typical scenario during upgrade is that RemoveExistingProducts is sequenced
early. The upgrade therefore needs to apply versioning
The event viewer might have a notification what Component requires source.
If not, then a verbose log file will definitely show it. That'll tell you
quickly what is th eissue.
On Thu, Nov 4, 2010 at 11:01 AM, Pally Sandher wrote:
> Is the upgrade shipped as an MSI or an MSP? I've seen that happen
Is the upgrade shipped as an MSI or an MSP? I've seen that happen with
MSP's when doing stuff like deleting files from the new version without
authoring an appropriate RemoveFile.
If it's an MSI are you using a bootstrapper to deploy it or just the raw
MSI?
Palbinder Sandher
Software Deployment
I have been unable to recreate this issue here, but I am getting
reports of users attempting to upgrade to the next version of our
product getting a dialog to browse to the location of the previous
version's MSI file, which is no longer where the installing user had
it.
This is causing the upgrade
The error tells you exactly what you are doing wrong. It says you must schedule
the custom action *between* InstallInitialize and InstallFinalize. You are
scheduling them *after* InstallFinalize.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
F
It's nothing to do with WiX. Recursive MSI-based installs don't work when
called from the execute sequence (that's what error 1618 is about) and
launching them from the UI sequence makes silent installs impossible (and that
means group policy deployment too, IIRC).
Phil Wilson
-Original
well we did this fine in WIX 2.0
so it shud be able to be done in WIX3.0 too
Vasu
On 4 November 2010 16:00, Chris Lord wrote:
> Vasu,
>
> If the additional application has its own installer then you have no
> option except to use a bootstrapper as you can't start one installer
> from within anot
In article ,
Rob Mensching writes:
> Correct, the website publish process is really flimsy. It's been in place
> since 2005 and heavily based on XSL which Fredrik (who built the process)
> loves but I hate debugging. Some XML escape character is probably missing.
I tried to look at the code
Vasu,
If the additional application has its own installer then you have no
option except to use a bootstrapper as you can't start one installer
from within another (called chaining).
Can't help with the second part I am afraid.
Chris
On 11/04/2010 11:46 AM, Vasu Chakkera wrote:
> Dear All,
>
Dear All,
I am new to WIX and trying certain things.. I have successfully finished
writing an installer that does most of the things..
I now have a situation where as a part of installation , i need to check the
presence of MathPlayer.exe in the system, and if it doesnt exist, then i
need to insta
Hi,
First of all the path C:\WINDOWS\System32 should be C:\WINDOWS\SysWOW64
where C:\WINDOWS can be any path where Windows is installed.
Therefore you should use the appropriate properties.
Secondly, using "RD ..etc.." implies the use of the commandline which is
(imho) bad practice..
So basically,
23 matches
Mail list logo
