|
 |
asp_components thread: COM Component fails in ASP page
Message #1 by "Ian Short" <i.short@w...> on Tue, 26 Sep 2000 16:07:30 +0100
|
|
I have created a ActiveX COM component (in VB5) which acts as a wrapper
around a non-ActiveX dll. My component (which appears to be correctly
registered on the server) works perfectly within a compiled VB project but
not when called from within an ASP page. I have even taked the ASP script
and (with very slight amendments) ran it as a Windows Scripting Host
script which also worked perfectly.
Is there anything extra I need to do in order to get a COM component
working successfully within ASP?
Thanks,
Ian Short
Message #2 by Imar Spaanjaars <Imar@S...> on Tue, 26 Sep 2000 18:15:04 +0200
|
|
Might be a stupid question, but did you register the component on the
server as well? Are the webserver and the "compiler" two different machines??
Imar
At 04:07 PM 9/26/2000 +0100, you wrote:
>I have created a ActiveX COM component (in VB5) which acts as a wrapper
>around a non-ActiveX dll. My component (which appears to be correctly
>registered on the server) works perfectly within a compiled VB project but
>not when called from within an ASP page. I have even taked the ASP script
>and (with very slight amendments) ran it as a Windows Scripting Host
>script which also worked perfectly.
>
>Is there anything extra I need to do in order to get a COM component
>working successfully within ASP?
>
>Thanks,
>
>Ian Short
>
Message #3 by "Ian Short" <i.short@w...> on Wed, 27 Sep 2000 10:08:03 +0100
|
|
Yes the component is registered on the server ok. The WSH script that I
tested it with was executed on the server itself, as well as the VB
compiled project, so I know that the component works it just doesn't work
within an ASP page.
|
|
 |