That's a managed code exception, so what exactly are you doing? You've got a
managed form being shown and you're collecting data from it and parsing it?
I'm thinking you have a dependent assembly that isn't installed yet (in the
GAC).
The "normal" way to get this data is to collect it in the actual UI sequence
with an Add Dialog, adding the Customer Information dialog to the dialogs
and collecting the name there from the USERNAME property, passing it to a
custom action if you need it there. Perhaps this is what you're doing, but
that managed code exception means that you have a managed code custom action
somewhere - MSI doesn't do managed code without custom actions of some kind.

Signature
Phil Wilson [MVP Windows Installer]
----
> Hello,
>
[quoted text clipped - 9 lines]
>
> Jake
Jake Smythe - 10 May 2006 15:38 GMT
Phil,
I did create a UI sequence and am trying to pass the information from
the setup UI to the managed code dll but the setup bombs prior to getting to
the dll from the custom actions area. Is there a sample (preferably in
vb.net) that is doing this correctly? I can capture information during setup
from the UI provided the user doesn't put spaces in the textbox.
Jake
> That's a managed code exception, so what exactly are you doing? You've got
> a managed form being shown and you're collecting data from it and parsing
[quoted text clipped - 21 lines]
>>
>> Jake
Phil Wilson - 10 May 2006 16:34 GMT
There isn't a sample that will work if you have a dependency on an asssembly
that you're installing in the GAC, there are some difficulties in that area.
My assumption is that your custom action is marked as an Installer class CA
in its properties, and you're passing CustomActionData something like
/something=[USERNAME], but you'll need to give more information than just
that you're getting an FileNotFoundException. Is this a ServiceInstaller
class? What's your exact string that you're passing to CustomActionData.
Typically these FileNotFoundException issues occur when installing something
like a service with managed code custom actions because there's already
unseen data being passed, and your CustomActionData gets in the middle of it
and the internal parsing fails when trying to find your assembly. I wonder
if it's even getting as far as your Install method - do you know?
I'll add that managed code custom actions can have some difficulties.
http://www.installsite.org/pages/en/msifaq/a/1044.htm

Signature
Phil Wilson
[Microsoft MVP-Windows Installer]
Definitive Guide to Windows Installer
http://apress.com/book/bookDisplay.html?bID=280
> Phil,
>
[quoted text clipped - 32 lines]
>>>
>>> Jake