Hi all,
No need to reply now as I have the extra code to make the MSI installer
work. In the document quoted, the CustomInstaller project required some more
code than was evident in the document mentioned in my previous post.
The keyword in that document was "component" of the title "Installer
Component". When I created the CustomInstaller, I created it in VS .NET 2003
as a Class Library to create the DLL. What was not automatically added was
the Component-side of this project, code which I got from Graham McKechnie -
thanks.
Regards,
Neville Lang
"Neville Lang" <neville@MAPS_ONnjlsoftware.com> wrote in message
news:%23Pjl9tE%(E-Mail Removed)...
> Hi all,
>
> For deploying a C# CF app, I am using the .MSI approach listed in the
> document "Developing and Deploying Pocket PC Setup Applications.
>
> My problem is that when the .MSI file is processed and unpacked, it never
> seems to call my event handler in the CustomInstaller.dll file, even
though
> this file is connected to the Install part of the Custom Actions of my
Setup
> project in VS.
>
> The CustomInstaller project is a C# .NET Framework DLL and I do not see
how
> by just assigning the DLL to Install in the Custom Actions section of the
> Setup project that it can call the AfterInstall event handler code in this
> DLL. Should there be a mapping somewhere assigning the AfterInstall event
to
> this handler code in the DLL? Has anyone else run into this problem?
>
> Regards,
> Neville Lang
>
>
|
Similar Threads
