Hi,
until rob implements this in 3.6 you might give nsis a try.
http://nsis.sourceforge.net/CABSetup_plug-in
So far Dominik
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Continuing-questions-about-WiX-tp5586332p5590478.html
Sent from the
Is that DLL a COM component? If such, is it self registering?
--- On Fri, 10/1/10, Alex Ivanoff alex.ivan...@shavlik.com wrote:
From: Alex Ivanoff alex.ivan...@shavlik.com
Subject: [WiX-users] Overwrite files with higher version on major upgrade
To: wix-users@lists.sourceforge.net
Date: Friday,
That's called a major upgrade. You need to change the product id for your newer
installer as well as the version.
You also have to say that you want previous version uninstalled. You have 2
options:
1. Use an Upgrade element like explained here. Remember to schedule
RemoveExistingProducts
Hi all,
my installer should set some environment variabes A and B.
Normaly i have to do something like this;
Directory Id=TARGETDIR Name=SourceDir
Directory Id=ProgramFilesFolder
Directory Id=INSTALLLOCATION
Name=MyDir
Component Id=Component1
The purists will tell you that you should never do this, and they are
mostly correct. If I had a chance, I would rebuild SomeFile.dll to be 3.0.1.2
( or higher ) even if I was using the same source code as the 2.1.0.0
version. Just apply another label and it's no big deal. But sometimes
Hi
Thanks to all of you for the help. I was not changing my product ID lol
thats why its was always saying that a newer version was installed.
But I found that this is not doing the same uninstall that Add/Remove
Program do. I have many custom action that create things (SQL Server
Database,
Blair Thanks for your comment
We are working on WIX 2.0 and have a wxl file. We use some strings that are a
part of WixUI_en-us.wxl while we have some other strings that are specific to
our product. We cannot have these as two separate files (i.e. we cannot use the
WixUI_en-us.wxl file for
Plain dll.
Sent from my iPhone
On Oct 1, 2010, at 3:33, fiordean dacian dfiord...@yahoo.com wrote:
Is that DLL a COM component? If such, is it self registering?
--- On Fri, 10/1/10, Alex Ivanoff alex.ivan...@shavlik.com wrote:
From: Alex Ivanoff alex.ivan...@shavlik.com
Subject:
Hello,
I have a problem with running an upgrade to newer version with Wix.
When i'm doing an upgrade from version 1.0.0 to version 2.0.0, at first
all files are updated.
But then after InstallFinalize all files except the files added during
the upgrade are removed.
Which means also the
I think you may have sequenced RemoveExistingProducts in the wrong place in
V2.0.0.0.
It either needs to be
InstallExecuteSequence
RemoveExistingProducts After=InstallValidate /
/InstallExecuteSequence
or
InstallExecuteSequence
RemoveExistingProducts After=InstallFinalize /
We dealt with the same problem in http://msiext.codeplex.com - wanting to show
the user a meaningful error message. All errors bubble up as exceptions and all
custom actions set the CA_ERROR property to the error message that usually
includes the error code.
Sanjay: did you write the CA?
You need a bootstrapper. Try http://dotnetinstaller.codeplex.com.
dB. @ dblock.org
Moscow|Geneva|Seattle|New York
-Original Message-
From: Fabien Costantini [mailto:fab672...@shaw.ca]
Sent: Thursday, September 30, 2010 2:43 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users]
Ok, its working now, I had to change the InstallSequence too
InstallExecuteSequence
RemoveExistingProducts After=InstallValidate /
Custom Action=CA_writePasswordInRegistry After=InstallFinalize
Overridable=yesNOT Installed/Custom
Custom Action=ConfigureWebApp
Hi:
I've got an msi that I'm writing, and I'm setting a property if an existing
non-msi install is present, if it is, I need to present the user with an
dialogue presenting yes/no choices, when yes is pressed run an executable and a
dll custom action then continue the installation. If no is
A launch condition displays a single message using a modal dialog box and
aborts
the install. Instead you'd have to write a custom dialog. But you can't
literally run the exe and dll right after because you are in the UI sequence
and you shouldn't make system changes until the execute
Hi,
I'm using wix 3.5 and the iisExtension (which is working really well),
however I'm unsure of how to handle IIS user changes on upgrade.
My upgrade works well, upgrading files etc as you'd expect. However if
a user has added a host header post-install, that change is not
maintained when an
Sometimes I wonder how a customer is supposed to know the right answer to these
kinds of questions anyway.
Phil Wilson
-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent: Friday, October 01, 2010 9:20 AM
To: General discussion for Windows
Hi:
I['m compiling differeing configurations. I need to reference a wixlib in the
installer which is build earlier in the solution build process. Can I use the
same variables as visual studio uses to reference the .wixlib file, in the
project, or is there another way?
Cheers
Sean.
When you have to replace strings, then yes, that is exactly the standard
practice for 2.0
-Original Message-
From: Naufal Basheer (Aditi) [mailto:v-na...@microsoft.com]
Sent: Friday, October 01, 2010 6:07 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re:
Version 2 should have all the files it wants/needs already contained in
itself (so that installing it by itself without ever installing version 1
would result in the complete file set).
-Original Message-
From: Simon Chromow [mailto:simon.chro...@bewotec.de]
Sent: Friday, October 01,
A WIXPROJ file is just an MSBuild file just like (almost) any other *PROJ
file used in VS, so yes, you can use the same VS/MSBuild variables the same
way(s).
-Original Message-
From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk]
Sent: Friday, October 01, 2010 10:51 AM
To:
Wow thanks a lot !
I just implemented a first iteration of this bootstrapper utility with my
msi installers and it really does the job for me !
I also found very handy the 'basic' ui mode which does not even make
necessary for the end user to interact with each installer ui.
Now, I read in the
Ok, I was able to successfully uninstall my products as well by adding an
installed check clause and also embedding the msi file, then finally
checking for the product upgrade id.
It seems that I can even detect older (non-msi) installs by checking for
filenames or directories !
Great tools,
I have an app that I've currently authored the setup to always install
unelevated per user. When I created my components to deploy files I had to
include a registry value in each one and make it the KeyPath of the component
to make the validation happy. Now I need to support a per machine
24 matches
Mail list logo
