Hello Happy New Year!
I was able to enhance my home theater with the big help from http://afcgb.net.
I recommended this to my friends.
Karl, 31, Germany
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForg
It appears that the reason for running RemoveExistingProducts after
InstallFinalize is to take advantage of file versioning rules: that the new
version of the product will have files in common with the old one, and
therefore that the new install will only replace or update files that need
it; unins
- Original Message -
From: wix-users@lists.sourceforge.net
To: [EMAIL PROTECTED]
Sent: Saturday, November 18, 2006 8:48 PM
Subject: The standard
purchased, take my daughter, and do not smile that I boast she isPuck, who
loved mischief to his heart, was highly diverted with thiswhen you f
John Robbins wrote:
> While the documentation says that there can be "(min: 0, max: unbounded)"
> RemoveExistingProducts under the InstallExecuteSequence element, if you try
> it, you get a "Duplicate symbol
> 'Actions:InstallExecuteSequence/RemoveExistingProducts' found." error
> compiling.
>
Anil Prasad wrote:
I have two different applications packages A and B. B is dependent on
A for its functionality. Now the issue is after installation of B, I
am not able to tell windows that unless B is un-installed don't let
anybody uninstall A.
I looked at MSI documentation and found a
Lynette Ooh Hooi Lin wrote:
Using wix toolset to register the dlls does not seem to work for my
installation. I have to register manually before it can work.
Tallow can't always detect every registry change. The workaround is to
use Tallow to generate the majority of the authoring then twe
6 matches
Mail list logo