Ah I didn't realise that, shame really 'cos it would work really well.
On uninstall FindRelatedProducts is run doesn't that populate the
upgrade table?
Mandar, You could use a registry search for the product/upgrade code but
it is not easy in my experience.
Neil
-Original Message-
From:
Do you mean the display order in the program file group? If so there
isn't any documented why to control that order (I think it is in
alphabetical order).
Neil
-Original Message-
From: subramanyeswari [mailto:sravi...@yahoo.com]
Sent: 15 June 2010 06:03
To:
Look at this control:
Control Id=Finish Type=PushButton ... Default=yes Cancel=yes
Text=$(loc.WixUIFinish)
It says whatever the localized WixUIFinish string is (I assume Finish)
and is the button clicked if you press the Enter key and the button
clicked if you press the Esc key. So,
Hello,
this is a working example of a COM object registration:
Component Id=COMComponent Guid=insert GUID here
File Id=DtmDll Source=YOUR_DLL_NAME_HERE KeyPath=yes /
Class Id={$(var.C_DtmClassId)} Context=InprocServer32
Description=$(var.C_DtmDll) ForeignServer=mscoree.dll
ProgId
Hi all:
I have created a msi with customized bitmaps (the company logo and all
that stuff). While doing a normal installation, the images looks good;
the problem comes when I try to make a patch: the msp file continues
using the default bitmaps.
In one of the files I've included the following:
Hi,
I mean my msi is not copying the files in the correct path(installed path of
an application) during modifying option.
How to get the installed path for an application during the install and how
to use that path during modify option of an msi.
Can any one give me an idea/example on how to
Thanks for the pointer.
Setting cancel=no fixed the issue.
-
Andy
BuildDeployment
Schneider Electric
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Pressing-ESc-Key-in-the-install-Finish-screen-tp5176628p5181151.html
Sent from the wix-users
Hi,
I search a good solution to upgrade an already installed .Net
application. In this .Net application we have standard xml-config files,
which has only settings with application scope. I have searched for many
forum entries and it seems that nobody has useful information about it.
The logic
Hi,
I have the following node (file.dtsConfig):
Configuration ConfiguredType=Property
Path=\Package.Variables[User::path].Properties[Value] ValueType=String
ConfiguredValue\\convs07\Historicalfile:///\\convs07\Historical
Integration\DataFarm\WIT\Files\/ConfiguredValue
Since I have a hybrid InstallShield / WiX environment, I typically import the
regfile into an IS Merge Module, build it, dark it and steal it.
- Original Message
From: Andy Clugston clug...@gmail.com
To: General discussion for Windows Installer XML toolset.
The old APIs will continue to work fine, even though they are deprecated. You
just need the updated config file in order to target .NET 4.
It looks like the main reason the old APIs are deprecated is because the new
set of APIs support loading multiple simultaneous versions of the CLR into the
The error says that it can't find the node specified by the XmlFile/@XPath. The
syntax looks correct. I wonder if there are XML namespaces involved here.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please
Your XML is malformed:
ConfiguredValue\\convs07\Historicalfile:///\\convs07\Historical
Integration\DataFarm\WIT\Files\/ConfiguredValue
Should be either:
ConfiguredValue![CDATA[\\convs07\Historicalfile:///\\convs07\Historical
Integration\DataFarm\WIT\Files\]]/ConfiguredValue
Or
Author your installer package as a Major Upgrade. That will give you a package
that can do fresh installs and upgrades.
Xml schema/content migration is something I haven't figured out how to do
acceptably within a MSI package. I'm very interested in hearing how others
tackle this problem.
I have an XML config file which is shared by three products. Each installer
currently uses util:XmlFile actions to put appropriate information in the
config file. When only one product is installed, this works fine, but when
two or more are installed, the last one installed clobbers the config of
The other thing to worry about is that RegAsm on an assembly will generate a
type library and register it. RegAsm /regfile will create you a reg file but
will not generate any type library Interface entries. Whether this matters or
not depends on your COM interfaces, but if it does matter then
I have a question: How would you prefer to associate a .REG file with a
binary if you were harvesting an entire directory? Are your .reg files named
the same as your .dll/.exe files?
-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent: Tuesday,
If your base XML file (as shared by all three products) is fairly static,
you should be able to create a shared component (a component where the GUID
and the directory are the same for all three products). If your XML
transformations can be applied in any order, you shouldn't have any
problem
Hi there,
I have the following setting: 1 merge module, 1 product
The merge module contains an ini file which has to be updated based on
user Input form a custom dialog.
So we have the following situation: There is a property named CMSHOST
which contains the respective value that should be
Look in a verbose log. It is possible that INIPATH has the merge module's GUID
appended to it in its name.
-Original Message-
From: Jonas Kahlert [mailto:jonas.kahl...@docufy.de]
Sent: Tuesday, June 15, 2010 4:58 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Modify Ini
FindRelatedProdcuts returns without doing any work (a verbose log tells you
it is because it is a maintenance installation).
I wrote a custom action one time that parsed the Upgrade table and set
properties (at the time I called it FindRelatedProductsMinor). It might be a
good candidate to throw
I'm assuming you are not trying to change your install directories in your
maintenance transaction.
Already installed components should be correctly repairing in the location
they were previously installed into. Components that were not previously
installed as well as custom actions that use
Hi,
I would like to include 3 party program into my installer as below
(wix 3.0).
Binary Id=installer SourceFile=setup-couchdb-0.11.0.exe
/
CustomAction Id=couchInstall BinaryKey=installer
ExeCommand=setup-couchdb-0.11.0.exe /DIR=quot;[INSTALLDIR]couchDB
quot;
Thanks Blair that is useful to know (I can see it in the uninstall log
now I look closely).
Mandar, I think the other place to look is the key
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\UpgradeCodes but you
need to convert your UpgradeCode to a compressed GUID.
Neil
-Original
24 matches
Mail list logo