Is the install an MSI or an EXE? ( Or an EXE inside a self extracting EXE? )
The term you are most likely for is "repackaging" and it's not something WiX
is really geared for. You'd want something more like InstallShield ( or
InstallShield AdminStudio ) with it's Repackager program.
If thi
Can Wix be used to automate a vendor-supplied install?
The install is interactive - values are entered and buttons are clicked.
In my favor, all responses are the same for all users.
I want the Wix install to automate all responses, requiring no interaction.
Thanks,
Gary
I added a simple WiX project to my Visual Studio 2010 solution, added an MVC
web site and a Win32 Service as project references. I set the reference
properties to automatically Harvest.
When the MSI was built, just the .exe and .pdb from the Service was included,
but not the project ouput refer
Just wanted to say thanks for all the advice : the WIX_UPGRADE_DETECTED
condition worked well.
Sent: Monday, August 01, 2011 9:31 AM
To: 'wix-users@lists.sourceforge.net'
Subject: Major upgrade opt-out ?
We would like to be able to uninstall an older product, and install the new
version. I tri
That worked!
Thanks,
Atul
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: Thursday, August 04, 2011 1:58 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Fileshare permissions
I reproduced your problem using your code a
Hi Rob
I guess I've found the reason...
http://nsis.sourceforge.net/Docs/AppendixD.html#D.1
Quote:
Note that uninstallers copy themselves to the temporary directory and
execute from there so the original uninstaller can be deleted. This means
the error level the uninstaller sets is not available
For anyone interested, I found my own answer:
http://www.joyofsetup.com/2007/05/30/feature-conditions-and-ui/
Thanks to Bob Arnson for the great blog!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Remove-feature-through-ARP-tp6653020p6653794.html
Despite all of the great suggestions, I wasn't able to get this to work on my
machine, so I went and tried it on a VM, and everything worked correctly! I
know, I know, I should only do installer testing on a VM. I've learned my
lesson.
Anyway, thanks for all of the help! Now I get to go try t
I found the cause of this, though I do not understand why one worked and the
other not.
This machine had SharePoint installed (for development), and it also had a web
site at port 80. That web site was stopped, and the default web site (also at
port 80) was running.
One Wix project installed
I am struggling with a repeatable but not consistent problem. I am a new WIX
user on 3.5.2519 integrated with Visual Studio 2010 on Windows 7x64.
I am trying to install a web application including configuring the virtual
directory and web application itself. I have done this before, and have
Joe
As you can see below, I actually use WixUI_Common but I have customised
it with a slightly different sequence that includes an additional dialog
I added. My UI section includes all the customisation code as well as
the property.
Pally is right though (and
Have you set the ConfigurableDirectory attribute on the Feature?
...
Dave Connet
> On 08/04/2011 10:57 AM, Joe Tilley wrote:
>> I'm using WixUI_InstallDir as the installer UI, and it pops up with my
>> INSTALLDIR as the default directory as it should, but when I type in a
>> different directo
Yes, I'll check the verbose log. For some reason I always forget to do that.
I'm using ProgramFilesFolder, which should be the 32-bit folder no matter which
type of machine it's installed on. Also, the package is x86.
Thanks
_
Joe Tilley
FW Murphy
Software E
Chris,
I'll give that a shot. You're adding the Property element directly to the UI
element, not as a child of the UIRef element?
Thanks
_
Joe Tilley
FW Murphy
Software Engineer
Office
(918) 317-4130
Email
jtil...@fwmurphy.com
-Original Message-
Fr
Joe,
My setup has INSTALLDIR property inside the UI section itself rather
than on own, like this
...
...
<\UI>
And this works fine for me. Can't hurt to try it.
Chris
On 08/04/2011 10:57 AM, Joe Tilley wrote:
> I'm using WixUI_InstallDir as the in
Your code snippets look perfectly fine to me. I use code which is identical to
all intents & purposes which works fine.
However I would check a verbose log to see what's actually happening. Are you
trying to install an x86 MSI to an X64 location (as in "Program Files" rather
than "Program Files
I'm using WixUI_InstallDir as the installer UI, and it pops up with my
INSTALLDIR as the default directory as it should, but when I type in a
different directory name into the text box, or browse to a different directory,
it doesn't seem to accept it. Even though it looks like you're changing t
After some more reading, I switched to using the MajorUpgrade element instead
of authoring my own upgrade table, and now everything work with no error, even
when I upgrade from a Full Install to a lesser install.
I guess the MajorUpgrade element is auto-authoring the Upgrade table correctly.
S
I have been trying to determine why my WiXlibs do not provide the files
for the consuming project. I have been poking around in the WiXlibs and
explored them some with the Library and WixEnumerateCab classes.
I have discovered that the files in the cab within a library are named
0-n. I have not
Wix setup also uses a managed bootstrapper. This basically allows us to use
WPF UI to drive the bundle installation.
Wix setup however bootstraps .Net install in the bundle. I would like to
have some support in Burn that would allow me to fail the installation if
the required .Net version isn't fou
I don't know exactly what it's for - I believe it's used as an ID in the
generated transforms and possibly elsewhere. I know it's ok to change it if
you start producing patches from a new baseline MSI. Every time we issue a
new service pack as an MSI, I change the baseline to match (RTM,SP1, SP2
et
I am setting the OutputName element based on a command line property set during
the call to MSbuild.
The strange thing is that the error only occurs when upgrading from a "full
install" to a "subset install". If the upgrade is done with the same feature
set, there is no error, and if the upgra
Hello Everyone,
I am using the "Purely Wix" method for patches. Below the Media Element in the
Patch.wxs file, there is a PatchBaseLine element with an ID attribute.
I wonder what the ID attribute is used for except to reuse it on the -t command
line parameter for Pyro?
I have the issue that if
Rob, thanks so much for yor quick response! I was able to get selective
uninstall to work.
However, I discovered another issue with Burn feature selection in general
(both install and uninstall case). I noticed that unless it's the first time
installing the product or a complete uninstall, Burn do
Hi Michael, Thanks for the reply
The bold line is the CA in the below extract
This is the sequences.wxi :
!Databases=2 And &Databases=3 And Not SQL08DIR
PATCH And Installed
PATCH And Installed
Just on the off-chance.. did you rename any of your msi files ? You get that
error if you do.
-Original Message-
From: Joe Tilley [mailto:jtil...@fwmurphy.com]
Sent: 03 August 2011 21:04
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to handle conditional features on upgrade
I reproduced your problem using your code and ran into the same problem.
When I removed the permissions and just added "GenericAll", it worked.
-Original Message-
From: Atul Kolhatkar [mailto:atul.kolhat...@microsoft.com]
Sent: 03 August 2011 20:22
To: General discussion for Windows Inst
27 matches
Mail list logo
