Sorry about that.
The "problem" was that my extension DLL was not on the path.
I had assumed that if the DLL was deployed in the virtual root that would be
enough, but no.
[quoted text, click to view] "Andy" <swarb70sok@hotmail.com> wrote in message
news:3fa7ce56$0$19080$afc38c87@news.easynet.co.uk...
> I have an ATL 7 web service. I need to call methods in an MFC extension
> DLL.
> I have wrapped the extension DLL with a 'normal' (_USERDLL) MFC dll and
> linked my web service to the normal DLL. There is code in the
> InitInstance() of the MFC application in the 'normal' DLL which calls the
> initialisation code of the extension DLL (so that MFC resources etc are
> correctly located).
>
> When I try to call the web service the LoadLibrary() is failing with the
> error 1114 (ERROR_DLL_INIT_FAILED).
>
> I am using Visual Studio project dependencies to link the various DLLs.
> That is to say I have a solution with the ATL web service, a normal MFC
dll
> that has an instance of CWinApp and an MFC extension DLL that has and
> exported initXXX method. I have set the solution dependanies such that my
> web service depends on the normal MFC dll and the normal MFC dll depends
on
> the extension DLL.
>
> My questions are:
>
> 1) Is loading an MFC dll from a ATL server 7 web service dll a valid thing
> to do? If not, why not?
>
> 2) Assuming that the answer to 1) is 'yes', and the MFC dll that you load
> needs to use an MFC extension DLL, are there any special considerations
that
> need to be taken into account when initialising either the MFC DLL or the
> MFC extension dll?
>
> 3) Assuming the answer to 2) is 'no' - any other ideas why my web service
> DLL fails to load? If I remove the links to the MFC DLL's it loads and
runs
> just fine.
>
> TIA
>
>
> Andy
>
>
>