Hi,
I've noticed a strange behavior using burn. And I have no idea, how to
analyse it. Here's what happend:
Wix-Version: 3.6.2221
Test-Environment: Windows 7 Professional x64 running inside of
VirtualBox 4.1.4 with Additions.
Installation-Package: Burn with 2 msi-packages (created with wix)
Hello everyone,
I need to create a multi-language installer for a windows application. I
need help in creating an installer using WiX, which does the following
during installation:
1. Prompt user for language selection.
2. Proceed with installation in selected language.
3. Skip the
Hi,
It's hard to answer without your wxs, but for the WixUI_Mode, I would say you
need to make a PropertyRef instead a Property.
-Message d'origine-
De : Neville Lewis [mailto:neville.le...@gmail.com]
Envoyé : mardi 8 novembre 2011 10:10
À : wix-users@lists.sourceforge.net
Objet :
There's not enough information there. Can you post the original and updated
source code ? Possibly the patch wxs too.
-Original Message-
From: justin hull [mailto:justin.h...@assetpoint.com]
Sent: 07 November 2011 22:19
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Fragments
Thanks for your answer. I actually think it's not necessary but we want to
try it out for the scenario the guy who creates our big main wxs file has
no idea about the dependencies between all the projects and we can define
them somerwhere else.
I just found the DependencyExtension and tried to
Phil the bug is that the path returned by FileSearch is of the format
C:\Directory\Filename.ext\
The trailing slash after the filename makes the path returned by FileSearch all
but useless unless you use a custom action to remove it first, in which case
you may as well just use a custom action
AFAIK the DependencyExtension is about dependencies between installer
packages.
I'm solving component dependencies with groups. Like this:
Component Id=A.../Component
Component Id=B.../Component
ComponentGroup Id=GroupA
ComponentRef Id=A /
ComponentRef Id=B /
/ComponentGroup
Feature
One thing to keep in mind is that if you're targeting Windows Installer 5.0
it's only available on Windows 7 Server 2008 R2.
4.5 is the latest available redistributable for earlier Windows versions.
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F:+44 (0) 141 945 8501
Just tried uninstalling from control panel, without bootstrapper. Same
problem.
Here's the complete log:
Error 1402. Could not open key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WwanSvc\Profiles. System error
5. Verify that you have sufficient access to that key, or contact your
support
That perhaps explains the strange behavior of the DependencyExtension :D
Any possibibilty then to set one ComponentGroup as optional?
I'm thinking about having an ComponentGroup with Binaries and one with the
Program Debug Databases. Then the Debug dbs will be kind of addition to the
Binaries.
AFAIK you cannot do that with ComponentGroups.
If you like a flat structure you can do something like this:
Feature Id=Binaries
...
/Feature
Feature Id=Debug
FeatureRef Id=Binaries IgnoreParent=yes /
/Feature
This will install the Binaries-Feature when Debug or Binaries is
selected. It's
wix If you are looking for financial independence look no further
http://.todayl0newsi.com
--
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
Thanks, I think this will fit when i get this working.
I tried:
Feature Id=Binaries Title=Binaries Level=1
ComponentGroupRef Id=Host.Binaries /
/Feature
Feature Id=Symbols Title=Symbols Level=2
FeatureRef Id=Binaries IgnoreParent=yes /
ComponentGroupRef Id=Host.Symbols /
/Feature
But
I am tasked with writing an installer to deploy some (.NET) web services on
IIS. Typically the deployment will involve some/all of the following:
During install selecting:
. The App pool (test that the AppPool the user chooses is compatible
with the service/application being installed)
Finally, here's what happend:
The MSI contains a RegistryKey which references another RegistryKey by
id ( Key=[OtherKey]\SubKey ). By I removed the id attribute from the
other RegistryKey. So the references property does not exist. I assume
it expanded to SOFTWARE\Microsoft\WwanSvc\Profiles.
Here is the source file... cleaned up a bit
?xml version=1.0 encoding=UTF-8?
That makes sense. The files are large so I will upload them.
Original base install
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n6974348/TabWareXiTools8200.wxs
TabWareXiTools8200.wxs
project for full install for patch (upgrade)
With burn, what is the difference between the DetectCondition and
InstallCondition on the ExePackage element? I noticed that the NetFx4.wxs
file in the WiX sources uses DetectCondition to seemingly prevent
installation of .Net4 if it is already installed - but isn't
InstallCondition the same?
I did a quick diff of the 2 wxs files. The changes appear to be in a
component whose keypath doesn't change. I think, by default, in Wix v3+ the
first file/registry key in a component is taken to be the keypath unless one
is specified explicitly.
Unless the component's keypath changes, the
I've not looked at Burn but I would guess you could install something under a
wider variety of conditions that it just being already present or not. For
instance you might want to install a package based on OS or language or on
the presence of other products.
-Original Message-
From:
The DetectCondition helps you know whether the package is installed or not.
The InstallCondition allows you to choose to install a package even if the
DetectCondition is true, or to choose not to install a package if the
DetectCondition is False.
I use it because I have to install SqlExpress
Am I right in deducing that InstallCondition, if specified, will override
DetectCondition? So if InstallCondition=False, the package will not get
installed regardless of DetectCondition. Likewise, if
InstallCondition=True, the package is always installed regardless of
DetectCondition.
or is
For the first part, I can say yes. I have not tested yet the second assumption,
but I hope it works as you (and I) expect it.
Regards,
Nicolas Penin
-Message d'origine-
De : Aled Hughes [mailto:trestlemon...@gmail.com]
Envoyé : mardi 8 novembre 2011 16:56
À : General discussion for
Thanks for the input. It got me looking in different directions. I found this
link which is interesting for it both advocates the need to break MS rules on
one file per component while stating it is the preferred method (sigh).
http://makemsi-manual.dennisbareis.com/component_keypath.htm
In
You have a number of options depending on what your constraints are.
The easiest upgrade type to write is a major upgrade with an early scheduling
of RemoveExistingProducts. It's much more tolerant of mistakes.
Moving to 1 file per component is another option. That way, the keypath of
each
You have a number of options depending on what your constraints are.
The easiest upgrade type to write is a major upgrade with an early scheduling
of RemoveExistingProducts. It's much more tolerant of mistakes.
Could you point me in the right direction for this? I have both Phil Wilson's
MSDN section on major upgrades
http://msdn.microsoft.com/en-us/library/windows/desktop/aa369786%28v=vs.85%29
.aspx
Wix help file
How to Guides - Product upgrades - Implement a major upgrade in your
installer
Wix Tutorial
http://wix.tramontana.co.hu/tutorial/upgrades-and-modularization
Alex
Bob Arnson-6 wrote:
In addition to admin images, you can use Melt.exe to build an image you
can use without -ax.
I thought Melt only http://wix.sourceforge.net/manual-wix3/AllTools.htm
dealt with merge modules (.msm). Special use, maybe?
- John
--
View this message in context:
I use this type of search in WiX 3.5 successfully but I have not tried to
confirm its behavior in WiX 3.6.
Property Id=SQLCMDEXE
RegistrySearch Id=SQLCMDEXE Root=HKLM Key=SOFTWARE\Microsoft\Microsoft
SQL Server\100\Tools\ClientSetup Name=Path Type=directory
FileSearch Name=SQLCMD.EXE/
Mmm, odd. I just did a standard AppSearch/FileSearch using only the MSI tables
and a search for msi.dll in the System folder does not return a trailing slash
on the end of the file name, using MSI 4.5. WiX doesn't get in the middle of a
standard file search does it?
Phil Wilson
As part of my installer I need to uninstall some other application which is
being superseded, prior to installing the new app. So into my .wxs file
I've added in:
Upgrade Id={UpgradeCode_of_other_application/
In the hope that the application will be removed. However, it appears not
to work.
1) detect the old application and set a property;
2) Use that property in a Launch Condition. Stop the install if present with a
Please remove the-old-product first; else continue with the install.
Unconditionally removing a product without the user's intervention is not
friendly behavior.
--
I'm using WiX 3.6.2221.0 and am having problems trying to build using
msbuild.exe. Most of the time the build is failing with
System.ArgumentException:
light.exe : error LGHT0001: Illegal characters in path.
[C:\cygwin\home\mymsi.wixproj]
Exception Type: System.ArgumentException
Stack
Thanks - you are quite right in that I should prompt first. In this
particular situation the other app is one that has very limited internal
distribution and I just wanted to make the transition as seamless as
possible to our users.
My original problem (of the item going into the upgrade table)
Using the default UI for the new Wix 3.6 Burn bootstrapper there is a
Options button that allows users to select an installation directory.
Questions about this I have are:
a) How is this referenced from within a chained MSI?
b) Can it be pre-set to a directory rather than blank?
c) Can the
In WiX 3.5, I am trying to create an MSI that can do both per-machine
(ALLUSERS=1) and per-user (ALLUSERS=) installs from the same MSI. In
this case, I want the default behavior to be per-machine, unless the
user takes explicit steps to install per-user.
I read several forum posts (and some of
Hi,
One of the localized languages in my setup msi is Arabic. (An Arabic transform
that is embedded in the Setup.msi)
When a text string ends with a special character (For example: C:\Program
Files\Company\) the special character gets moved to the beginning of the string
for Arabic only.
Any
Hello,
I have a generic dialog that uses an indirect property for a username and I
would like to enable and disable the Next button depending on whether a
username has been entered.
MyDialog.wxs
...
Dialog Id=MyDialog ...
Control Id=Foo Type=Edit ... Property=Dialog.Username Indirect=yes
I think it's my mistake. The property was also declared in directories.
However, if I remove it, it's never assigned. Must be missing something in the
installexecutesequence. Sorry to have made you loosing your time.
Sent from my iPod touch
Le 8 nov. 2011 à 18:58, Wilson, Phil
39 matches
Mail list logo
