Search results for query: *

nope

It's just a tool that allows you to select a DLL you want to run as a web service, which creates an ASP handler page and the appropriate WSDL and WSML files. I think it is this handler page that handles instantiation of the Web service DLL - it uses a SoapServer object (to handle soap...

I dont think we can wrap the SOAP functionality up like that - the SOAP toolkit is an app that takes a DLL (must be DLL and not EXE) and generates the ASP handler and WSDL/WSML files to make it a web service. Its SOAP (the Soap server?) that handles instantiating the web service DLL (i think)...

> In turn, our DLL instantiates the third party DLL in the Class_Initialise and destroys it in the class_Terminate method. i meant 'our EXE' not our dll

Thanks Bob. SOAP Toolkit requires a DLL, so we've created a DLL that wraps the functionality of the ActiveX EXE (which uses the third party DLL). Our wrapper DLL instantiates the EXE object in the Class_initialise and destroys it in the Class_terminate method, and has wrapper methods for the...

I have a web service (written in VB6 compiled to a DLL) , and I need to use a single instance of a third party DLL in the code - ie create the object and all 'hits' on the web service use the same instance of the object rather than creating new instances. Do you have any ideas of what...