Callback function seems not to work in MSDE setup

Hello, I'm installing MSDE and I can't seem to get the callback function to work properly. My program behaves as if the callback function is not being called at all. As a result, when the setup fails I only get the 1603 return code and no information on w
hat went wrong.
I understand from the documentation that the callback function has to have the signature
UINT __declspec(dllexport) callback(HANDLE hinstall, UINT uExitCode)
and be stored in a DLL created by the ExtendedStoredProcedure Dll option in Visual Studio .Net. Also, the Dll has to be stored in the temp directory and referenced as dll name!function name on the command line. All this is true for my callback. But the ca
llback seems never to be called. Any idea what could be going on, or how I can investigate?
Thanks.
I thought that the callback was just the same as a standard Windows DLL
callback function (which is probably the same as an Extended Stored
Procedure). You might try using depends.exe to see what name your DLL is
actually using to export the function, just to make sure it's not being
mangled in any way. Also make sure that you use the GetTempPath API to get
the temp directory.
Jim
"Jon Webb" <anonymous@.discussions.microsoft.com> wrote in message
news:A98E4BD8-9F24-4B50-885B-13C426190862@.microsoft.com...
> Hello, I'm installing MSDE and I can't seem to get the callback function
to work properly. My program behaves as if the callback function is not
being called at all. As a result, when the setup fails I only get the 1603
return code and no information on what went wrong.
> I understand from the documentation that the callback function has to have
the signature
> UINT __declspec(dllexport) callback(HANDLE hinstall, UINT uExitCode)
> and be stored in a DLL created by the ExtendedStoredProcedure Dll option
in Visual Studio .Net. Also, the Dll has to be stored in the temp directory
and referenced as dll name!function name on the command line. All this is
true for my callback. But the callback seems never to be called. Any idea
what could be going on, or how I can investigate?
> Thanks.
>