Regarding:
        <UI>
          <EmbeddedUI Id="MyCustomUI" 
SourceFile="$(var.MyCustomUI.TargetDir)$(var.MyCustomUI.TargetName).CA.dll"/>
        </UI>

If you don't specify a "Name" attribute, the Id is used.  I tried defining my 
embedded UI the same as yours and it didn't work; had these lines in the MSI 
log:
        MSI (c) (34:7C) [20:12:54:750]: EEUI - Running MsiEmbeddedUI code
        MSI (c) (34:CC) [20:12:54:765]: Cloaking enabled.
        MSI (c) (34:CC) [20:12:54:765]: Attempting to enable all disabled 
privileges before calling Install on Server
        MSI (c) (34:CC) [20:12:54:765]: Connected to service for CA interface.
==>     MSI (c) (34:7C) [20:12:54:812]: EEUI - Unable to load embedded DLL 
handler

When I added the ".dll" extension, things worked fine, for me.  (so...)
        <UI>
          <EmbeddedUI Id="MyCustomUI.dll" 
SourceFile="$(var.MyCustomUI.TargetDir)$(var.MyCustomUI.TargetName).CA.dll"/>
        </UI>


Also, if you put your embedded UI within the same project as a managed custom 
action; that would be the next thing to correct.  The build process won't look 
for your UI handler if the assembly has managed CA's within it.  If this is the 
case, what'd I recommend you do is create a new managed custom action project, 
then delete the CustomAction.cs file, then rename the CustomAction.config file 
to EmbeddedUI.config.  Then add your embedded UI handler class which implements 
the IEmbeddedUI interface to the project, etc... then try and build.

Then, what you'll want to verify from a Visual Studio command prompt, "dumpbin 
/exports %your assembly%.CA.dll" looks something like this:

-----------------------------------------------
  Section contains the following exports for SfxCA.dll

    00000000 characteristics
    489F4510 time date stamp Sun Aug 10 14:44:16 2008
        0.00 version
           1 ordinal base
          20 number of functions
          20 number of names

    ordinal hint RVA      name

          1    0 00001091  = @ILT+140([EMAIL PROTECTED])
          2    1 000010A0  = @ILT+155([EMAIL PROTECTED])
          3    2 0000108C  = @ILT+135([EMAIL PROTECTED])
          4    3 0000109B  = @ILT+150([EMAIL PROTECTED])
          5    4 00001096  = @ILT+145([EMAIL PROTECTED])
          6    5 0000105F  = @ILT+90([EMAIL PROTECTED])
          7    6 00001064  = @ILT+95([EMAIL PROTECTED])
          8    7 00001087  = @ILT+130([EMAIL PROTECTED])
          9    8 00001082  = @ILT+125([EMAIL PROTECTED])
         10    9 00001109  = @ILT+260([EMAIL PROTECTED])
         11    A 00001078  = @ILT+115([EMAIL PROTECTED])
         12    B 00001069  = @ILT+100([EMAIL PROTECTED])
         13    C 00001073  = @ILT+110([EMAIL PROTECTED])
         14    D 0000106E  = @ILT+105([EMAIL PROTECTED])
         15    E 00001055  = @ILT+80([EMAIL PROTECTED])
         16    F 0000105A  = @ILT+85([EMAIL PROTECTED])
==>      17   10 000010F5 EmbeddedUIHandler = @ILT+240([EMAIL PROTECTED])
==>      18   11 00001104 InitializeEmbeddedUI = @ILT+255([EMAIL PROTECTED])
==>      19   12 00001023 ShutdownEmbeddedUI = @ILT+30([EMAIL PROTECTED])
         20   13 00001005 zzzzInvokeManagedCustomActionOutOfProcW = 
@ILT+0([EMAIL PROTECTED])

  Summary

        5000 .data
        2000 .idata
       16000 .rdata
        5000 .reloc
        1000 .rsrc
       6B000 .text
-----------------------------------------------


If lines 17,18, 19 look like the below (prefixed with "zzz"), something still 
be wrong...

         17   10 000010F5 zzzEmbeddedUIHandler = @ILT+240([EMAIL PROTECTED])
         18   11 00001104 zzzInitializeEmbeddedUI = @ILT+255([EMAIL PROTECTED])
         19   12 00001023 zzzShutdownEmbeddedUI = @ILT+30([EMAIL PROTECTED])


===============================================


If all of the above look good but your UI still isn't launched, the next step 
would be to look at a verbose windows installer log file to attempt to diagnose 
what's wrong (if you can attach one and your matching embedded UI handler code, 
etc... I'll try to help you through this).


Let me know how this turns out for you...





-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Crum
Sent: Saturday, August 23, 2008 9:53 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Anybody know how to use EmbeddedUI?

Thanks for the reply John. I guess the question is, what is an example of
Wix XML that will use/launch my embeddedUI dialog.

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Nannenga
Sent: Saturday, August 23, 2008 12:23 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Anybody know how to use EmbeddedUI?

I've spent a bunch of time lately regarding UI handlers, including embedded
UI.  Where can I be of assistance (did you have particular questions I might
answer)?


________________________________________
From: [EMAIL PROTECTED]
[EMAIL PROTECTED] On Behalf Of Andrew Crum
[EMAIL PROTECTED]
Sent: Friday, August 22, 2008 6:58 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Anybody know how to use EmbeddedUI?

I got the EmbeddedUI sample in the DTF directory to compile (I also have
Managed Custom Actions compiled and working just fine using DTF).



I got this far:

<UI>

  <EmbeddedUI Id="MyCustomUI"
SourceFile="$(var.MyCustomUI.TargetDir)$(var.MyCustomUI.TargetName).CA.dll"/
>

</UI>



But I'm at a loss for how to actually use my embeddedUI vs. the normal
built-in UI.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to