Hi,
If you want to execute a component ONLY during a certain first install and
not repair/remove (very useful with SQL scripts), do the following:
Component Id=YOUR-ID-GOES-HERE Guid=YOUR-GUID-GOES-HERE KeyPath=yes
Transitive=yes
ConditionNot Installed/Condition
The condition will ensure to
Component Id=YOUR-ID-GOES-HERE Guid=YOUR-GUID-GOES-HERE KeyPath=yes
Transitive=yes
ConditionNot Installed/Condition
On Sun, Oct 5, 2008 at 1:45 AM, Sandeep Gautam (HCL Technologies Ltd)
[EMAIL PROTECTED] wrote:
No, I did not use this attribute.Shall I mark this attribute as No ?
I have tried this option also. On repair/repair, with this option it is
deleting the data base . But On remove/repair, I don 't want to do any with
this component on repair/DB(component which is creating DB at the time of
installation).
Please help me out.
Regards
Sandeep
-Original
Sandeep,
If you are using this to work with databases, I would suggest you a
different approach. I am creating my databases using SQLScripts elements,
and not using WIX's SQLDatabase element. That way, I have a better
granularity of what I want to do, particularly regarding the way I create
the
Hello.
I'm new to installers and wix in particular, therefore, maybe, stupid
question, but I didn't find answer on the surface.
I have a product 9for which I want to make an installer) that consists of:
1. kernel-mode driver, that is root-enumerable pnp device (software only);
2. accompanying
Hi,
I want to limit the UI to open for the second MSI installer.
So, do I write a Custom Action for it. Or are there any Launch conditions
available in Wix which can do that job?
In case of Custom Action which condition do I need to check.
Thanks.
Regards,
Kamal
Date: Wed, 01 Oct 2008
Hi:
I need to add registry entries when/if a checkbox is checked on my
finish page.
I also need these entries to be removed during uninstallation if added
diring installation.
What is the best way of achieving this?
Cheers
Sean.
wow, that would be very nice :-)
I use mondo and I want to insert my dialog right after the license agreement
dialog.
-Ursprüngliche Nachricht-
Von: Bhavdeep Singh [EMAIL PROTECTED]
Gesendet: 04.10.08 21:54:18
An: General discussion for Windows Installer XML toolset.
Hi guys,
I am using WiX 2.0. I have a custom action dll which is written in C. The
custom action doesn't get executed. Even though I checked that its function
ordinal
number is really 4. My dll is 9KB in size but my MSI is only increased by 1 KB
with the custom action added. I have checked
Thanks Eithan, But I just want to know what ever I am using is this known open
issue or I am giving some thing wrong condition.
Regards
-Sandeep
-Original Message-
From: Eitan Behar [mailto:[EMAIL PROTECTED]
Sent: Sunday, October 05, 2008 12:25 AM
To: General discussion for Windows
Hi guys,
I got the error as below,
2Project d:\xx\xx\Installer\MakeInstaller.proj (default targets):
2Target BuildInstaller:
2 d:\xx\xx\Installer\MakeInstaller.proj(43,9): error MSB4067: The element
sources beneath element candle is unrecognized.
2Done building target BuildInstaller in project
I am still trying to decipher the proper use of SQLDatabase on all
scenarios, install, upgrade, rollback, etc. If you manage to work it out,
let us know.
-Original Message-
From: Sandeep Gautam (HCL Technologies Ltd) [mailto:[EMAIL PROTECTED]
Sent: Monday, October 06, 2008 5:02 AM
To:
Shao Voon,
Your attachment didn't come through, but I'm curious: why are you trying to
hand-author build process for this? WiX ships with a complete build process for
building WiX projects using MSBuild. See the topic Using WiX with MSBuild in
the Wix.chm file that ships with your install.
Sean Farrow wrote:
I need to add registry entries when/if a checkbox is checked on my
finish page.
I also need these entries to be removed during uninstallation if added
diring installation.
What is the best way of achieving this?
There's no way to add registry entries after installation
Michael Faden wrote:
I'm trying to install Votive 2.0.5805 on XP (32bit) with Visual Studio
2008 Professional Edition installed.
Votive v2 supports VS2003 and VS2005, but not VS2008.
I used the X64-Version of Votive on
another box and it worked perfectly.
That's the WiX v3 installer,
Sergey Abakumoff wrote:
Control Id=SamplesBrowse Type=PushButton X=304 Y=100
Width=56 Height=17
Cancel=yes Text=Browse...
...
The problem is if I click on X(close window) button, then BrowseDlg is
opened instead of CancelDlg!
What I am doing wrong?
MSI is treating
Ian Elliott (Excell Data Corporation) wrote:
If I condition out the component that contains the scripts, it doesn't get
installed during major upgrade. I see in the log that ComponentRegister then
registers that component as State=-7. When you finally uninstall, the
component does not get
Bryan Turner wrote:
Media Id='1' Cabinet='product.cab' EmbedCab='yes' /
Make sure you set the Package/@Compressed attribute to 'yes'.
--
sig://boB
http://joyofsetup.com/
-
This SF.Net email is sponsored by
fluorite wrote:
The above example created a short cut properly but I want to change the
default console shortcut properties such as QuickEdit mode, background color
and etc. Shortcut doesn't seem to have attributes to change these options.
Anyone knows how to do this? Is this even doable using
Edward Forgács wrote:
From testing, it seems that the setting of the property in the UI is
completely ignored, i.e., the installer has already made up its mind as to
whether the component will run or not. The files either get removed every
time, or never.
When you uninstall a product,
20 matches
Mail list logo