I found the following resources looking at this:
In 2002, a file called MDAC Merge Module.doc contains links to a sample
MSM (that won't work on Vista w/ UAC AFAICT) along with instructions to
change it from the included MDAC 2.7 (no idea which release) to whatever
other version you wish to
I assume that the dialog would contain a listbox and a custom action of your
writing would populate it.
There have been discussions on this list regarding using custom actions to
populate listboxes, as well as dialog refresh issues.
-Original Message-
From: Sankha Biswas (Extended
We use Wix 3.0. The problem is, some Spanish characters don't show correctly.
instalación shows as instalaci?n.
Some background:
Our product requirement asks us to support multiple language MSI which isn't
supported officially by MSI. Someone posted some
Hi Blair,
Could you please fwd me the discussion thread.
I would appreciate your help.
Thanks,
Sankha
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Wednesday, October 28, 2009 11:21 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users]
You will likely notice, if you open the MSI in Orca, that when you check the
codepage for the database it isn't the codepage you likely expected it to
be. The codepage used has to support the characters you intend to use. If
you don't set it, it defaults to 7-bit ASCII. Transforms should be able
One that continued into this week has the subject (whitespace varies) of
[WiX-users] How to populate a list box in a msi dialog duringruntime --
thread started by Uma Harano [mailto:uhar...@esri.com] on Oct 12th. I
believe the thread includes the refresh issue as well.
-Original Message-
Hello,
by clicking Next in a Dialog window as MyDialog the ExitDialog is appearing
two times.
I am using Wix_Mondo.
Publish Dialog=ExitDialog Control=Finish Event=EndDialog
Value=Return Order=9991/Publish
Publish Dialog=MyDialog Control=Next Event=NewDialog
Value=ExitDialog1/Publish
what can be
Um http://wix.sourceforge.net/manual-wix3/WixUI_customizations.htm ?
Also exists in your WiX.chm installed with the WiX toolset on your local
machine.
You may want to go through the tutorial as this is also covered at
http://www.tramontana.co.hu/wix/lesson2.php#2.3
Palbinder Sandher
Software
Hi Blair,
Here I would like to explain you the reason why I use this Custom Action. This
CA is to call an exe to start some services. For the old path, the services are
already started. If start them again, it will cause problem. For the new path,
the exe must start the services, otherwise the
Heat can't extract the COM information from your executable but never
fear, all is not lost quite yet.
I've used a tool called RegSpy2 to harvest the /regserver information
from an out-of-process COM server executable in the past. It's available
at http://www.installsite.org/pages/en/msi/tips.htm
Luckily for you someone else asked the same question 5 hours before you
did.
See my answer to the thread Heat and .exe COM objects.
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 with
You should look at what your application needs installed to run rather
than what InstallShield does in the package it generated.
Before I joined IES our packages were created by the IT manager (he
'managed' a team consisting of himself) in InstallShield. They were
massively bloated with a lot of
http://msdn.microsoft.com/en-us/library/aa368569.aspx
Exit Dialog is shown by the InstallUISequence. You're also showing it
before that when a user clicks the Next button on your MyDialog.
Follow the MSDN instructions to replace the Exit Dialog in the
InstallUISequence with your MyDialog.
Are these services as in Windows Services, controlled by the Service Control
Manager? They have APIs that let you discover the run state of controlled
services, as well as the fact that you can ignore the failure to start when
the result is that the service is already running.
If you must
Hi Blair,
Thanks a lot for your help.
I will try to use the path search custom action as you said. I am not clear how
to create a custom action native dll. I just create an empty project in Visual
Studio 2005. Add your code to .cpp file:
#include windows.h
#include msi.h
#include msiquery.h
Just a general installer question, though I am using Wix 3.0.
I have created a .MSI with no UI - I use this to turn it into a Bootstrap
installer package, and as such don't want it to have any UI.
I am also creating patches of this installer, for periodic updates. All
that does work fine.
Hi Blair,
I googled how to create custom action dll. And the link error has been resolved.
Now the question is how to complete the function as you suggested.
Regards,
Chunyan
-Ursprüngliche Nachricht-
Von: Jiang, Chunyan (GE Healthcare)
Gesendet: Donnerstag, 29. Oktober 2009 14:50
For both dialogs, they just need to exist in the MSI (either by themselves
or via the MSP). Also, a populated InstallUISequence must exist so that UI
can be enabled (same). If the UI elements are in the MSI, they will be used
when the MSP is applied if needed.
-Original Message-
From:
All -
In my installer I validate data on a dialog by performing a
DoAction event (calling a custom action) on a next button press. It can take a
minute or more to validate so I need to either display a popup dialog saying
Validating - Please wait... or display the text on top of
Hello
I created an installation and upgrade MSI files using WIX.
(Which was relatively easy).
I am testing the upgrade msi.
if the original MSI (Xyz.msi) is present in the original path the
upgrade is done smoothly. I am using the command: msiexec /i
XyzUpgrade.msi REINSTALL=ALL
Hello
Thanks for the quick response.
I think I am using different GUIDs.
in the original MSI it is
Product Name='CapsCake' Id='D497344E-D020-4DD8-B2CD-653287D8DA80' ...
int the upgrade it is
Product Name='CapsCake' Id='D34C4CCF-495E-453E-9F7A-5A8CEC65643F'
Should I replace the guide of each
Hi all,
Background :
I'm trying to build a Prerequisites dialog with a ListView in it. As
such I'd like to make the functionality of this dialog as generic as
possible, so it can be reused across several installers, so that all our
installers have a common look and feel. This also gets around
The subset of SQL used by MSI is documented here
http://msdn.microsoft.com/en-us/library/aa372021(VS.85).aspx
Could read the whole table and used a regex on each row ? It would be a
managable size.
-Original Message-
From: Dominique Louis [mailto:dominique.lo...@amxeurope.com]
Sent: 29
Generally not. The Component's guids should be stable (if a component
contains the same things, only newer, being installed, it generally should
keep the same guid). Only if you change the name or path of the file/key of
the component's keypath (if you only have one file/registry item that will
be
Thanks
The problem was solved using your inputs.
giora
Blair wrote:
Generally not. The Component's guids should be stable (if a component
contains the same things, only newer, being installed, it generally should
keep the same guid). Only if you change the name or path of the file/key of
the
I was trying to avoid bringing back the whole table, but as you say it
can't be too big.
Thanks for the SQL link as wel..
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: 29 October 2009 16:24
To: General discussion for Windows Installer XML toolset.
Hi,
I have created a property that gets the value for the 'Start' element.
Property Id=STARTTYPE Value=disabled /
The compiler returns following error:
: error CNDL0022 : The ServiceInstall/@Start attribute's
value, '[STARTTYPE]', is not one of the legal options: 'auto', 'demand', or
'dis
When during the uninstall are the RegistrySearch values evaluated?
Are they evaluated during by uninstall package that is invoked during
a major upgrade as well? If so, when?
On Fri, Oct 23, 2009 at 8:17 PM, Blair os...@live.com wrote:
Yes, it is.
-Original Message-
From: Tony
I'm trying to install some project item templates for Visual Studio and need
some other custom actions, so am building the installer with WIX. I want the
templates installed for all users, not just the current user. VS looks for
the templates in a known directory structure under the Documents
I was able to figure this out and have a working version. The key was
simply to filter the BuiltProjectOutputGroupDependencies ItemGroup based
on the CopyLocal metatdata. Can i just post some code or is it necessary to
go through the sign an agreement submit a patch to the dev list type
The StartType field in the resulting ServiceInstall table is DoubleInteger, so
a [property] isn't a legal value (it would require the field type to be
Formatted).
Phil Wilson
-Original Message-
From: eneo [mailto:e.karagj...@gmail.com]
Sent: Thursday, October 29, 2009 11:51 AM
To:
I think you might as well create your own custom table, then you would return
all the entries as well as define other information in the table (description,
how to install etc).
Phil Wilson
-Original Message-
From: Dominique Louis [mailto:dominique.lo...@amxeurope.com]
Sent:
Type of serviceinst...@start attribute is not Formatted
(http://msdn.microsoft.com/en-us/library/aa368609(VS.85).aspx). So, depending
on when decision has to be made on this attribute's value:
- Build time
Use preprocessor directives to set variable and use it something like this:
When during the uninstall are the RegistrySearch values evaluated?
RegistrySearch is evaluated during AppSearch action.
Are they evaluated during by uninstall package that is invoked during
a major upgrade as well? If so, when?
Uninstall during major upgrade is done by RemoveExistingProducts
I'm testing out Burn and the setup.exe that it creates doesn't seem to do
anything when I double-click on it. I took one of the example Burn tests and
my manifest looks like:
BurnManifest xmlns=http://schemas.microsoft.com/wix/2008/Burn;
Log Level=debug Mode=append Path=c:\BurnLog.log /
Stub
The database field behind the Start attribute is not a formatted type (or
other type that allows replaceable values. If you can't know what startup
type you will want/need, though, you can use Bob's semi-custom action
technique to change that field at runtime.
-Original Message-
From:
You need both
PropertyRef Id=WIX_DIR_COMMON_DOCUMENTS/
and
Directory Id=WIX_DIR_COMMON_DOCUMENTS
as well as including the WixUtilExtension reference.
-Original Message-
From: Brian Noyes [mailto:brian.no...@gmail.com]
Sent: Thursday, October 29, 2009 12:19 PM
To:
For the installing user, you can use the SendToFolder property as a
directo...@id
(http://msdn.microsoft.com/en-us/library/aa371615(VS.85).aspx).
Altering profiles that are not loaded breaks roaming profiles in a really
bad way (which may be why the initial release of Vista didn't include in
Realize that uninstall during major upgrade involves two different packages
being transacted (the only nested transaction still supported). The
upgrading package runs, and during its RemoveExistingProducts action the
InstallExecuteSequence of the package(s) being removed are run with the
REMOVE
Thanks,
Have done as you suggested (use RegSpy2 then Tallow then RegCop) but
have run into three problems which make it hard to automate.
Firstly RegSpy2 throws a File not Found message box up which you have
to click ok on (it still works), if you look in the code there is
comment which says
By the way for anyone thinking I should generate the WiX xml by hand,
the WiX output from the suggested method (RegSpy2 + Tallow + RegCop)
produces 700 lines of xml. If you have several of these ActiveX exes to
register like I do then doing this by hands would involve writing
several thousand
This isn't directly answering your question but if you are willing to continue
living with VBScript you could ask it for the folder path.
(http://msdn.microsoft.com/en-us/library/0ea7b5xe(VS.85).aspx)
-Original Message-
From: Evan Beeton [mailto:ebee...@informasoftware.com]
Sent:
Hi Blair,
I appreciate your response.
I just tried the solution you provided. I've made a big progress:
when I compile each language, I added something like -cultures:fr-FR because
in our language file we have this line WixLocalization Culture=fr-FR.
Then I got the msi, I opened it with Orca.
Tom Crozier wrote:
In my installer I validate data on a dialog by performing a
DoAction event (calling a custom action) on a next button press. It can take
a minute or more to validate so I need to either display a popup dialog
saying Validating - Please wait... or display
In one of your wxl files for pt-BR, you need to change WixLocalization
Culture=pt-BR to WixLocalization Culture=pt-BR Codepage=860
-Original Message-
From: little.forest [mailto:little.for...@ymail.com]
Sent: Thursday, October 29, 2009 4:54 PM
To: General discussion for Windows Installer
The string in uninstallation: Are you sure you want to uninstall this product?
This string is always in English. Is it possible to translate it to other
languages? I can't find it in the language file WixUI_en-us.wxl. Or it may be
provided by MSI service?
Thanks.
/Brian
Error1Item has already been added. Key in dictionary:
'reg4E1AB2B932815062605C8450DBB987C0' Key being added:
'reg4E1AB2B932815062605C8450DBB987C0'light.exe0
I did find some references to this on the web saying its a bug
47 matches
Mail list logo
