Blair & Rob,
I appreciate you both taking the time to explain how MSI (and subsequently WiX)
interact with this problem space. That type of foundational knowledge isn't
found in manuals. I'll be able to rethink a couple parts of my installer now.
---
IIRC the error dialog will be suppressed, but the text that would have been
in the dialog will be in the error log.
-Original Message-
From: Richard [mailto:legal...@xmission.com]
Sent: Wednesday, July 28, 2010 1:48 PM
To: WiX Users
Subject: Re: [WiX-users] Executing user-interactive stuf
In article ,
"Blair" writes:
> What is considered best practice is to fail the installation attempt from
> InstallExecuteSequence with an error message indicating that the previous
> product must be removed first. This should then show up in error logs which
> would give the corporate clien
In our installer we would like to allow the users to select install directory.
However, we want to install it one directory off of user's choice. i.e. if the
user chooses c:\ we want to install it to c:\MyApp.
I am able to achieve this with
.
.
Our product has two features First o
I'd also add that it's taken us quite a while to come up with mechanisms to
handle the creation stable identifiers. It wasn't until late in WiX v3.0
that we really got it. We tried adding the auto-harvesting to Votive but
there were too many bugs to get it stable (VS2010 shipped and we need a
stabl
Haven't we always said setup development IS development? Seems like
stackoverflow proper with the tags we already have is the way to go. Seems
like
Area 51 would be for competely other subjects like scuba diving or something.
Christopher Painter, Author of Deployment Engineering Blog
Have a
In your Media element, make sure you don't have a Cabinet or
CompressionLevel attributes and that your EmbedCab attribute is "no" or
non-existent. In your Package element, set the Compressed attribute to "no".
And make sure that none of your File elements contains a Compressed element.
Note that i
Windows Installer has severe limitations when it comes to files being
added/removed arbitrarily from installations that will cause problems like
orphaned files, etc. This is due to some of the architectural decisions at
its core.
To overcome those limitations, requirements such as yours can only b
The error is before that point in the log. Look for a line where some action
is said to return a "3".
-Original Message-
From: Spencer Berry [mailto:sbe...@eidpassport.com]
Sent: Wednesday, July 28, 2010 2:37 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Uninstall Error: Fai
> Bear in mind that heat.exe isn't a substitute for actual setup
> development. It's a tool to make doing things (initially) easier
> especially for people migrating from things like InstallShield where
> there's a lot of stuff hidden from/done for you in the background.
I'm not trying to be cri
Hi All, currently when I build by WIX installer (using candle and then light),
it creates a single setup.msi for me. What I need is to create a single
setup.msi but all the files that I need to install should not be present in
setup.msi. I need them to exist separately and setup.msi should pick
Hi All, currently when I build by WIX installer (using candle and then light),
it creates a single setup.msi for me. What I need is to create a single
setup.msi but all the files that I need to install should not be present in
setup.msi. I need them to exist separately and setup.msi should pick
Ah I forgot about that! To repent for my wrong answer, there seems to be
a good discussion about it here:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Multiple-I
nstance-Transforms-Walkthrough-Proposed-Simple-Addition-to-WiX-to-Make-T
hem-Easier-td708828.html.
Neil
-Original
Would this be instead of the mailing list, rather than as well as it or
gatewayed to it like the existing nabble interface? If so, I'd hate the idea,
can't stand these horrible "web-based forums".
Regards,
jjf
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: Wednes
I'm new to WIX, and I've inherited a project that uses WIX for building the
installer. During UN-install, the installer ends with a message that it has
ended prematurely due to an error. Looking into the Installer Debug/Log file I
see the following messages:
Action 10:35:31: RollbackCleanup.
What is considered best practice is to fail the installation attempt from
InstallExecuteSequence with an error message indicating that the previous
product must be removed first. This should then show up in error logs which
would give the corporate clients a chance to deal with situation.
-Ori
Often this happens when versions of the files are not correctly set. That is,
your patch contains one file that has changed (i.e. binary comparison will show
differences) but version number of dll or exe was not changed.
However, if you read install documentation (and some blogs) in depth, you w
Hi,
As written in some other posts I have written A DLL for MSI which
detects my old setup program, asks the user if he wants to deinstall and
deinstalls the old product.
However, the old setup application does not offer a silent uninstall.
Right now, I call the DLL after LaunchConditions in *
I love this idea. I was actually looking at using their hosted solution for
a while then they took it off the market. I didn't realize they opened a new
way to get the same thing.
On Tue, Jul 27, 2010 at 5:20 AM, Yan Sklyarenko wrote:
> Hello WiX Community,
>
> I'm sure you know about StackOverf
Am 28.07.2010 19:09, schrieb Blair:
> #2: Add the InstallScope="perMachine" attribute to your Package element.
> This will add the ALLUSERS property for you.
Is there an advantage/disadvantage about
1
?
Regards
Luke
--
Hello fine WiX-Users!
Here's my dilemma, I'm testing patch creation with WiX. I take my setup.msi
and make a patch (msp) for it. The patch is something simple, such as changing
an .ico file. The patch works great. When I uninstall the patch, it prompts
for the original MSI. If you target
There is instancing support made available through WiX, but you have to
predetermine the number of instances you support (it isn't an unlimited
number) and the ProductCodes have to be manually updated in your authoring.
The feature is called "instance transforms".
The MSDN documentation starts her
I don't think you can do that without having multiple installs. That is
how SQL2005 worked, each install was its own msi (all 64 of them IIRC).
Neil
-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com]
Sent: 28 July 2010 00:38
To: General discussion for Windows Inst
Look at the heat tool.
-Original Message-
From: CPAJChambers [mailto:cchamb...@cryptontechnology.com]
Sent: Wednesday, July 28, 2010 1:37 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Element to harvest all files in a directory
Hi there,
Thanks for reading!
Just a quick
#2: Add the InstallScope="perMachine" attribute to your Package element.
This will add the ALLUSERS property for you.
-Original Message-
From: Kumar Deepak [mailto:kdee...@microsoft.com]
Sent: Wednesday, July 28, 2010 12:46 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Need
You may have to clarify which product you're referring to here because
UPGRADINGPRODUCTCODE is set in the old product if it is being uninstalled
because of an upgrade. If you're trying to influence the behavior of the old
product as it uninstalls then it may well be too late. The uninstall seque
I was looking at a log of one of my installers while poking around with
something in the InstallUISequence & noticed that the longer it sits in
the InstallUISequence, the bigger the log file became. Looking through
the log I found there are repeated instances of "Note: 1: 2727 2: "
throughout it s
You can use an XSLT to transform the output from heat.exe by supplying
it with the -t parameter without any need for a custom application if
you need that functionality.
Bear in mind that heat.exe isn't a substitute for actual setup
development. It's a tool to make doing things (initially) easier
Ah almost. The problem was quotes around the values,
&F_SrePlugins35="3" failed
&F_SrePlugins35=3 worked.
I finally have an MSI doing what I want! Thank you all most sincerly.
From: Pally Sandher [pally.sand...@iesve.com]
Sent: Wednesday, July 28, 2010 08
> Is there a WIX element that I can use within
> a WIX script that will pick up all of the files within a location,
As has been mentioned, use heat.exe. In Visual Studio, I have small C# app that
generates WiX source by taking the output from heat and slightly tweaking the
XML with LINQ. This
Try something like
I think that should work but it depends on when (if?) Windows Installer
re-evaluates the &Feature Properties. It normally checks that stuff
during CostFinalize which runs before the WelcomeDlg shows up in the
InstallUISequence so I'm not sure if it will re-evaluat
This is the part I was missing "Usually WXL files are known only to
light.exe, not to candle.exe, so culture can only be known long after the
preprocessor is done."
I use code similar to your example currently for other items. I was more
interested in being able to use WXL data in the statement
Yes.
http://schemas.microsoft.com/wix/2006/localization";>
http://schemas.microsoft.com/wix/2006/localization";>
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Error-using-common-Localization-String-IDs-tp5343712p5345673.html
Sent from the wix-us
Dear Blair,
Thank you. I will do it this way then.
I only changed the approach a little bit:
1.) One main file (and lots of fragments etc.)
2.) For each "version" an environment variable needs to be set, e.g.
set VER=personal
set VER=corporate
set VER=demo
3.) Inside the main file
No but you can use heat.exe to achieve a similar result. Plenty of
discussing on this list how to do exactly that, search the archives.
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 w
Hi there,
Thanks for reading!
Just a quick question really. Is there a WIX element that I can use within
a WIX script that will pick up all of the files within a location, instead
of me having to specify each individual file? Something like a FileGroup
element, where I just specify a SourceDir
1. Need to create a virtual directory under a website and map it to a
folder on local drive.
2. Need to make installed application visible to all users (instead of
only the user installing it)
Regards,
Kr Deepak
DETAILS:
1. Currently we are creating website like this
Hi,
Thanks. You are right. I removed these two line and still it worked. I think I
made 3-4 changes at a time so thought it might be correct fix. Thanks again.
Rahul
-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent: Tuesday, July 27, 2010 5:49
38 matches
Mail list logo