There are the following elements in one of the dialogs of my installer:
Edit controls, i.e.:
PushButton control that has Default attribute is set to "yes":
So, if user presses Enter key, then License control should be invoked.
However, if Edit control is focused and user presses Enter key,
public class MSITestManager
{
private IntPtr parent;
private Session fSession;
public event ActionStartEventHandler CustomActionStarted;
public delegate void ActionStartEventHandler(object sender,
ActionStartEventArgs e);
public void RunInstall(string PathToMSI, string Co
I am attempting to run installations from a test application. I am processing
the installer messages using an External UI Handler in the external
application and running the UI in silent mode.
I would like access to the session object during the installation and can't
see a way to do this using
Hi,
As Wix is command-line based, I think it is a good idea to run it from a script.
But: I cannot find any documentation concerning the return values of candle and
light.
Can anyone help?
Best regards
Matthias
--
Th
On Thu, 07 May 2009 15:59 +0200, "Reuss, Matthias"
wrote:
> Hi,
>
> As Wix is command-line based, I think it is a good idea to run it from a
> script.
>
> But: I cannot find any documentation concerning the return values of
> candle and light.
That's because (AFAICT) they don't return values.
Michael Urman wrote:
> Truly. However Windows Installer could theoretically add support for
> customizing the basic UI experience without requiring the shell to
> change.
>
Maybe. But why would they start a turf war with the shell team? All it
would do is ensure thousands of new packages that
Hukumchand Shah wrote:
> I am not understanding that which custom actions execute first.
>
Generate a verbose log; it will show you how the sequences tie together.
And of course the MSI SDK has a fair bit of documentation on the subject.
--
sig://boB
http://joyofsetup.com/
---
Here is the order:
- InstallUISequence (everything up to ExecuteAction)
- ExecuteAction in InstallUISequence calls InstallExecuteSequence (you can
think of it as a blocking function call. You will get control back after
all actions in InstallExecuteSequence are done)
- Any action scheduled after
To add to response from Curtis Jewell:
During installation WI is using in-memory copy of original MSI. As a
result, no changes to original MSI are allowed and changes can be made to
in-memory copy only. To indicate your intent to change in-memory copy use
TEMPORARY as Curtis suggested.
Alex
-
I'm getting this error msg:
ICE38: Component ApplicationShortcut installs to user profile. It's KeyPath
registry key must fall under HKCU. C:\Documents and
Settings\mcgeed.PASA\Desktop\Kiss2009r011_050609\DejaVu Setup\Setup.wxs
Source:
http://www.wixwiki.com/"/>
See
http://robmensching.com/blog/posts/2007/4/27/How-to-create-an-uninstall-shor
tcut-and-pass-all-the
Alex
-Original Message-
From: slmnow [mailto:slm...@hotmail.com]
Sent: Thursday, May 07, 2009 7:24 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Creating Internet Shorcu
On Thu, May 7, 2009 at 08:34, Bob Arnson wrote:
> Maybe. But why would they start a turf war with the shell team? All it
> would do is ensure thousands of new packages that couldn't be
> uninstalled silently, deployed via GPO, and major-upgraded in their next
> release.
I don't think it would be
Hi All,
After an upgrade to V 3.0.5217, I have the following error when I want to
create a MSI.
The "AllFilesWithCulture" parameter is not supported by the
"WixAssignCulture" task. Verify the parameter exists on the task, and it is
a gettable public instance property.
Do you know what the probl
Thank you guys both for so much. But would you explain more on how I can
specify my intention of modifying the in-memory copy of the MSI? When using
MsiDatabaseOpenView, I tried to use "UPDATE `Component` SET
`Component`.`Attributes`='256' WHERE
`Component`.`Component`='AuthPluginRegistry' TEMPORA
Hi all,
I learned today about the ARPINSTALLLOCATION property to make upgrade
easier. Since I did not use this in the previous version of the
installer, but am adding as a custom task in the new version, I need to
update my AppSearch process.
I sequenced the AppSearch after FindRelatedProd
If you have a wixproj file, you can use MSBuild and everything should be
taken care of.
If you don't have VS.Net, then sharpdevelop is free and supports creating
wixproj files.
-Original Message-
From: Reuss, Matthias [mailto:matthias.mr.re...@siemens.com]
Sent: Thursday, May 07, 2009 9:
Hi Karma,
Actually, after carefully re-reading your question, I don't think you can
achieve what you want. Only temporary tables, rows, or columns can be
modified. In your case you are trying to modify existing component's 64-bit
flag. Won't work. Besides, I think that 32-bit and 64-bit versio
Hello all,
Building msi fails with the following message: "A string was provided which
doesn't match the specified database codepage '1252'. Either set your
database codepage to match these characters, or change those characters to
ones that exist in the database's codepage."
The cause of this i
I tend to use this for codepage/culture/language values:
http://msdn.microsoft.com/en-us/library/ms776260.aspx. Having said that it
seems to indicated the 1252 is correct for Finnish.
Neil
-Original Message-
From: Natalia [mailto:natalia.gladk...@arcadia.spb.ru]
Sent: 07 May 2009 17:54
This may help:
http://robmensching.com/blog/archive/2007/04/27/How-to-create-an-uninstall-shortcut-and-pass-all-the.aspx
slmnow wrote:
> I'm getting this error msg:
>
> ICE38: Component ApplicationShortcut installs to user profile. It's KeyPath
> registry key must fall under HKCU. C:\Docume
There were changes to support neutral and fallback languages. Check the
help file for all the details. Eric spent a fair bit of time adding lots
of words and a couple pictures.
Mathieu Belin wrote:
> Hi All,
>
> After an upgrade to V 3.0.5217, I have the following error when I want to
> create a
This is an academic discussion here. AFAIK, the Windows Installer team
doesn't look for feature requests on the wix-us...@list.sourceforge.net
Michael Urman wrote:
> On Thu, May 7, 2009 at 08:34, Bob Arnson wrote:
>
>> Maybe. But why would they start a turf war with the shell team? All it
>
Hello, all:
I recently upgraded from Wix 3.0.3829 to 3.0.5217, in order to develop an
MSI for Windows 7.
I now get the error:
candle.exe : error CNDL0288: The variable 'Configuration' with value
'Release' was previously declared with value 'Release'.
The salient lines of my .wixproj
Did you read the help documentation about how to do multi-language
builds in the WiX.chm? It has changed a lot in the last year+ since you
last picked up a build.
Scott Button wrote:
> Hello, all:
>
>
>
> I recently upgraded from Wix 3.0.3829 to 3.0.5217, in order to develop an
> MSI for Windows
In case anyone's still wondering how to modify the in-memory copy of the MSI
database here are some pointers.
You can't do much with using SQL command to modify the database (using
UPDATE, DELETE, ...). If you want to modify a existing row, do the
following. First, open up the view containing the
I'm using the bootstrapper from MSI Factory, but that's it. In fact
I've uninstalled it after making a copy of the bootstrapper folder :)
Since we already had a license I took at look at using it to speed up
initial development and for doing some custom dialogs, but the
generated code is pretty ug
Is this deferred CA scheduled after InstallFiles? I can't tell from your
sequence number.
But as Brian pointed out before, you should not use batch files. If you're
writing registry values or copying files, use native authoring which is
transacted. Batch files are not transactional in nature. You'
It's better that you use a separate MSI. To determine the correct
installation locations, you can use a ComponentSearch to find some component
for your other product that determines the installation location, and then
use a type 51 custom action () to set the TARGETDIR.
Patching new components in
WiX patching does support adding new components, but those components have
to be added to features in your products as well. They should also be in new
Fragments.
But if those features are optional features, adding new components to
optional and possibly absent features will cause prompt for sourc
For public consumption, we still require the files during bind because we
only diff the files (including Binary and Icon objects) then after
filtering. For large products this saves a huge amount of time. The file
info in the transforms may not always be correct, especially when wixmsts
are created
Hey Marc,
To answer your question, you need to call MsiDatabaseCommit function after
you make change.
Understand that you cannot permanently persist the changes into the msi file
if you are doing
it from a CA of the running MSI. You can find more details here
http://msdn.microsoft.com/en-us/libra
Dear All,
I have created my own exe for uninstallation of application, which takes
care of showing custom pop-ups and taking respective inputs from user.
Basic idea behind creating my own exe is to modify default uninstall dialog
"Are you sure you want to uninstall this product?" when I try to uni
This property is intended to display the primary installation folder in
Add/Remove Programs. I'm not sure how it makes anything easier during
upgrades, as evident by the problems you're having. But it's just for
display. What exactly are you trying to use it for?
TARGETDIR is a required property,
Just made a quick check (WiX 2)- there are return values.
Candle.exe finished successfully (with some ugly CNDL1044 short name warnings)
- errorlevel 0
Candle.exe could not find its wxs file - errorlevel 1
Are there more details?
Regards
Matthias
> -Ursprüngliche Nachricht-
> Von: Cur
34 matches
Mail list logo
