Hi All,I'm trying to add a checkbox to the Finish dialog which will let me launch an application conditionallyI've tried adding a checkbox like so:Control Id=Launch Type=CheckBox Width=100 Height=17 X=135 Y=80 Property=LAUNCHCONFIGURATIONCHECKED
And then having Property
Based on the information provided below, youll
likely want to look into using the WixIIsExtension, WixSQLExtension, and
WixUtilExtension (for some additional service configuration and xml
manipulation custom actions).
Youll need to decide to use either
WiX 2.0 or 3.0. Were currently only
I have a shortcut componentin my setup package that fails ICE validation because it doesn't "use a registry key under HKCU as its KeyPath". I have the ALLUSERS property set to 1. This will set the ProgramMenuFolder to the "All Users" profile. Why does itstill need to have a registry key under HKCU
Hi Chesong,
Is there a way to supress the New Hardware Wizard when
CM_Reenumerate_DevNode is called? None of the parameters
can do it. I guess I have to ask this question in a forum; The Wizard
appears in XP, but not in Server 2003.
Best regards,
Calin
Chesong Lee wrote:
Refer to How
John Vottero wrote:
This is mostly tool for developer to get the cmdlet working. Release
setup
should set the registry keys explicitly.
See, it's not just WiX crazies!g
It just sets series of registry keys. We need to document the keys which
vendors need to set for registering
I see. How about just putting the
component into Feature1 so that it will run when Feature1 is installed locally?
Derek
From: Scott Sam
[mailto:[EMAIL PROTECTED]
Sent: Friday, July 28, 2006 5:12
AM
To: [EMAIL PROTECTED];
wix-users@lists.sourceforge.net
Subject: RE:
Refer to How To Force Reenumeration of a Device Tree From an Application
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q259697
if you want to go for your own custom action.
CM_Reenumerate_DevNode:
John Vottero wrote:
Are you saying that it's impossible to create a good Installer based
Installer class?
No.
That's fine with me, who do I start with? I just need some direction
from Microsoft. Right now, I have the PowerShell team saying use these
Installer based classes to install
Michael Cline wrote:
Is there any way to update the property with every key press?
No. Unfortunately, MSI only updates properties on focus change.
--
sig://boB
http://bobs.org
-
Take Surveys. Earn Cash. Influence the
Hi List,
is there any possibility to create a folder inside the system DRVSTORE?
When installing a driver, some files may reside in different folders and
the inf file
needs them from different locations. The problem occurs when the installer
copies these files to the DRVSTORE and the
Hello.
My installation package consists of MSI-file and set of directory with
additional files. Those files are used by type 1 custom action (DLL file
stored in a Binary table stream). Since these directory is required, in
MSI there is a property that checks for the directory existence (via
On Tue, 25 Jul 2006 08:27:37 -0700, Derek Cicerone wrote:
Hello,
This is a bit beyond my knowledge of the IIS custom actions. The
quickest way to find a solution is likely going to be debugging the
custom action yourself to see whats going wrong.
I have plenty of bandwidth, that's not the
When defining a component with "ProgramMenuFolder" as the directory path for a menu item, an ICE38validation error occur indicating that the component installs to user profile and that it must use a reg key under HKCU as its KeyPaths. Since I have the property ALLUSERS=1 set doesn't this indicate
I have a component that looks like:
Component Id=DbInstallationDirectoryService
Guid=A4B5E633-D715-4e8e-8C4A-E58D1BAFFBAE
XmlFile Action="" ElementPath=//DBInstallation/FeaturesInstalled
File=[DBCREATION]dbinstallation.xml
Id=dbInstallationConfig20 Name=Feature
Sequence=19 Value=Feat1 /
I backed out of this a couple of months back because I was having difficulties... Let me see if I can find it in my source-control... otherwise I can try and reproduce...On 7/26/06,
Rob Mensching [EMAIL PROTECTED] wrote:
I know that I had trouble with Component
referenceing because
My custom action in install the Microsoft Enterprise Library into the gac and
register all their Instrumentation classes. This is Microsoft code and they
have the installers in the code so I assumed it would be easiest to just call
them.
Let me ask you this. I am not a c++ developer by any
Hello, all!
I have following situation:
when I use Class element to install Class for my COM server, I use Server
attribute to set path to my COM server in registry (under InProcServer32 key).
I use unadvertised mode (i. e. Advertise=no) for Class element.
The problem is that WIX writes this in
Rick Glos wrote:
We just released version
5.0 of our product. Spending
6 weeks updating our installer (we have a custom C# installer). I can
see
our new customers
instead using a
new .msi for later versions (5.5, 6.0, etc). What do I do about our
existing customers when they
This is good, except for the part about not creating an Extension. smile/
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Vottero
Sent: Wednesday, July 26, 2006 5:32 AM
To: Bob Arnson
Cc: wix-users@lists.sourceforge.net; [EMAIL PROTECTED]
Subject:
Sorry about that everyone. These messages where posted two days ago when we were having problems with mail server at work. Hope not too many more come across. I dont want anyone thinking I'm flooding the mailing list.
Thanks
John
On 7/26/06, John Hidey [EMAIL PROTECTED] wrote:
Here is my
I used a similar approach to deal with migration of an app that was
originally built with non-MSI WISE and then did the same basic thing again
when my first MSI version was (mistakenly) installed per-user instead of
per-machine. AppSearch for traces of the old stuff and LaunchCondition that
James Carter wrote:
[exec]
E:\delivery\Dev\wix_public\src\ext\iisextension\wixlib\IIsExtension.wxs(70)
: error LGHT0102 : The localization variable !(loc.ConfigureIIs ) is
unknown. Please ensure the variable is
defined.
John Hidey wrote:
Is there
a way to do what I want
to do. I would think that this can be done. Many installers do this,
but
maybe they use a C++ custom action which does the registry for them.
Any
thoughts?
Or they just use standard MSI support for registration. Calling
Shmarya Rubenstein wrote:
InstallUISequence
Custom Action=LaunchConfig After=ExecuteAction
![CDATA[LAUNCHCONFIGURATIONCHECKED]]
/Custom
/InstallUISequence
After MSI has processed the ExecuteAction action, it stops following the
sequence in InstallUISequence.
If there are utilities to bring a pure WiX 2 code base
up to a pure WiX 3 code base then breaking compatibility is fine by me. We
do not intend to mix the two. The utilities would eliminate costly manual
conversion time and provide a quick way for the entire WiX 2 code library to be
As you've discovered, when you install a product a cached MSI file is
created, and maintenance activities use this cached MSI file.
It's the ProductCode guid that indicates that the product is already
installed on the system, and when a product is already installed MSI goes
into maintenance mode.
I am using the Enterprise Library in this
way as well. I decided to install the assembly into the GAC, also install the
assembly to somewhere on the file system and finally install a batch file which
is executed via a custom action after InstallFinalize that runs installutil
I know its
The very latest WiX 3.0 release fixes this, enjoy! :)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Andrey T
Sent: Friday, July 28, 2006 4:47 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Long path name to COM server
Hello, all!
I have
This question has been coming up
often. Note that ALLUSERS is completely uppercase so a user can
change your installation to be per-user via the command line or several other
methods. This means that you need the HKCU key to ensure proper repair
operation (since a shortcut is not a valid
We already have a tool to convert from WiX
2.0 to WiX 3.0. Its called wixcop. I assume you were
referring to converting the source code itself (not the wixlib files) since just
having the libraries without source is a bit dangerous.
We do not have a tool to convert from WiX
3.0 back
Title: SelfRegCost on windows 2003 Server
Its probably a missing
dependency. It might be easier to stop using self reg by running tallow
(wix v2) or heat (v3) against the self-reg dll to collect its registry keys. J
Derek
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On
To resolve the localization issue: I think
youll need to pass cultures:en-us to light to load the English
resources for the extension. This change was just made in the last
release.
Please note that the custom action code in
WiX 3.0 is identical to what can be found in 2.0. We still
32 matches
Mail list logo
