We are moving some current VB6 DLL functionality to a web service but still need to call it from clasic ASP.  There is some debate about weather to wrap the soap calls in a VB6 DLL or to simply declare the classes in the ASP page itself.  The reason for puting the classes directly into the ASP code are to prevent long running transactions from blocking each other and causing memory leakage.  However, doesn't a VB6 DLL in a COM+ application with it's MTSTransactionMode property set to 'UseTransactions' accomplish the same goal -- plus the benefits of complied code?  Any articles you could point me to about calling webservices via classic ASP will be greatly appreciated.