[WiX-users] How to refer to an icon from a tag

[Lewis G. Pringle, Jr.]

Suppose I have:

 



 

In my WIX source file. This produces - when I install - a .ico file
installed to

C:\Windows\Installer\{CLSID}\CCRFileIcon.ico

 

Which I can then refer to in a registry setting (say a file icon
specification).

 

The docs for the  element appear to indicate (along with the ICE
warnings) - that the Icon can only be used for Class, Shortcut, or ProgID
table and ARPPRODUCTICON.

 

But - since its getting installed to the hard disk, I cannot see
why I cannot refer to it as a property for a  entry.

 

So - I tried:

.



  



 

But that produces:

>error LGHT0204 : ICE03: Not a valid foreign key; Table: Registry, Column:
Value, Key(s): reg8AF95EB4B1F2B9056909B6CD8B7D7EF4

 

I can see that I'm trying to do is not documented to work, but I'm unclear
why its not possible? What is the preferred way to do this? I'm just
(related to my previous message) trying to write out the registry entries
needed for associations for my file types. I just want the icons to appear
with the files.

 

I'm unclear what the best way to do this is? I could add an 'icons'
directory - and actually install the icons as separate files in a
subdirectory under my application directory>? Is that better than using the
 WIX element?

 

Lewis. 

-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Very confused by the structure of ProgId/Verbs/etc - for non-trivial case of specifying file associations

[Lewis G. Pringle, Jr.]

Folks:

I understand how to use the ProgID for some simple cases, such
as this example:

 







  

  

  







 

 

The problem is - how do I structure things if I have multiple components. I
think I've exhausted all the possibilities, and they all seem to fail.

 

Suppose I have TWO components, PROGRAM_A, and PROGRAM_B. and both of these
programs operate on a filetype .MFT.

 

I could do something like







  

  







 







  

  







 

This runs into problems with the ProgId being duplicate defined. 

 

 

I've tried bundling the ProgId elements into a THIRD component, and then
using 

 

  

That fails because I cannot have the TargetFile references go
across components.

 

I could simply avoid using the Verb/ProgId/etc elements, and just use the
underlying REGISTRY elements for the parts of the registry I wanted changed,
but I saw ICE warnings in my existing WIX installer that suggested I should
be using these ProgId/etc elements.

 

Any pointers?

 

Thanks,

Lewis.

 

 

 

-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] WIX and private assemblies for Windows 2000

[Lewis G. Pringle, Jr.]

Folks:

I have an activeX control I deploy with my Win32 application
which requires registry settings. I've created a manifest for this OCX, so
that it can be installed on WinXP and later without any registry settings
(so works more nearly side-by-side with other programs that might use this
OCX).

 

The issue is with Win2k. Apparantly, the whole private assembly
trick doesn't work on Win2k, which means that I must have my installer do
the registry munging (add typelibs etc) on Win2k, but not later OSes.

 

The obvious way to do this was to create TWO components - one
the XP-And-Later one, and one for Win2k. I did this using:

 

   

  



VersionNT >= 501

  

..

 

  



   VersionNT = 500

  .

 

The trouble  is that I get warnings from WIX:

warning LGHT1076 : ICE30: The target file
'hqo8tfwc.man|GigaSoft.ProEssentials.Charting.manifest' might be installed
in '[ProgramFilesFolder]\Records For Living, Inc\HealthFrame
v3\GigaSoft.ProEssentials.Charting\' by two different conditionalized
components on an LFN system: 'GigaSoft.ProEssentials.Charting' and
'GigaSoft.ProEssentials.Charting.Win2k'. If the conditions are not mutually
exclusive, this will break the component reference counting system.

 

 

And so on - for each file in the two components.

 

This warning suggested to me that there might be some neater,
cleaner WIX way to solve this problem?

 

 

 

Lewis.

 

 

 

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Subclassing WIX dialogs

[Lewis G. Pringle, Jr.]

Folks:

It appears the standard methodology for making changes in
dialogs is to copy the dialog into your own .wxs file, and anything that
referred to it (like a UI sequence) also has to be copied and modified.

 

Are there any plans (maybe in Wix v3?) to include an ability to
do some sort of limited 'dialog subclassing'? where perhaps you could just
add a control?

 

For example, maybe something like:

 



  CD &Key:




 

 

Lewis.

 

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] OPTIONALLY start service after its been installed (Wix v3)

[Lewis G. Pringle, Jr.]

I'm using the latest daily build of Wix v3.

 

I have a windows service I'm installing, and I've found I can do:

 

  

 

To install my service without starting at installation time, or:

 

  

To get it to run automatically after installation.

 

 

Next, I added a checkbox to a configuration dialog:

 



 

And I tried to modify the  tag as follows:

 

  

 

Now I gather I might need to change the values of the checkbox to be
'install' or '', but that seems to miss the point, since it looks like the
wix compiler is rejecting having any variable string at all for the 'Start='
attribute.

 

Is there some other way I can make starting the service at the end of
install optional?

 

Lewis.

 

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] setup.exe has no icon?

[Lewis G. Pringle, Jr.]

Folks:

The setup.exe built using setupbld.exe in the latest
(3.0.3106.0) version of WIX doesn't include an application icon. Most other
installers appear to have some kind of installer icon.

 

Is this choice intentional?

 

I realize I can make a manual copy of the setup.exe 'stub', and
put an icon in myself, and then use that stub. But is there some reason WIX
doesn't provide an icon for the setup bootstrapper? Is there some reason its
not made more easy to override the icon (or provide one if there is none)?

 

 

Thanks,

 

Lewis.

 

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Permission Element, and next v3 pre-release build?

[Lewis G. Pringle, Jr.]

Folks:

I've just tried WIX, after a decade of suffering with
Installshield, and I'm truly impressed! This is a major improvement!

 

I'm using the latest WIX v3 pre-release build 3.0.2420.0.

 

One of the few (blocking) bugs I've run into appears to be a
known bug with handling the Permission element under registry entries.

 

http://sourceforge.net/tracker/index.php?func=detail
 &aid=1560158&group_id=105970&atid=642714

 

According to this link, it was actually fixed in January of
2007.

 

Since the last release (3.0.2420.0) was at the end of 2006, I
don't yet have this fix.

 

I was wondering, when is the next planned 'build' of the v3
series to be made available? Is there some way I can get the pre-pre-release
builds from CVS, and build the latest version myself (or is it too unstable
to make that worthwhile?)

 

 

Thanks,

Lewis.

 

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users