UINT __stdcall MyCA(MSIHANDLE hInstall)
and that the project output is set up within the File System and that it is
defined within the
Custom Actions page.
However, at build time, the .NET Deployment project can not find the
exported function
within the DLL.
Any ideas?
thanks
Paul
Anyways...I got it to compile and build without a problem. I just had to
move the
C++ DLL and build it within Visual Studio 6.0 instead of Visual Studio .NET.
I still can't get the install going as I am getting a File Not Found
Exception on a name
that I don't even have listed in my deployment.
When I tried rebuilding the deployment package in another location, the same
thing
happened and it appeared to have occurred on a word which I typed within the
"ProductName" or "Title" property.
It is really weird and I can't seem to figure out what is going on right
now.
Paul
"Phil Wilson" <Phil....@unisys.spamcom> wrote in message
news:uTiO5tD...@tk2msftngp13.phx.gbl...
If you're getting a .NET exception you haven't got the custom action set up
properly because MSI calling a C++ function has nothing to do with .NET.
Perhaps you left InstallerClass set True.
--
Phil Wilson [MVP Windows Installer]
----
"Paul Brun" <pb_new...@pbrun.net> wrote in message
news:OSN5WBEP...@tk2msftngp13.phx.gbl...
Thanks
Paul
"Phil Wilson" <Phil....@unisys.spamcom> wrote in message
news:uwStveEP...@TK2MSFTNGP09.phx.gbl...