We have a Com+ VB6 DLL used in our asp classic application. After upgrading to IIS 6.0 and Windows Server 2003 it seems to be causing us problem. How should we replace it with .NET (2.0) functionality?
Assume re-writing the asp classic pages is out of the question.
EDIT: If rewriting it as a com accessible assembly, won't this leave the same issues with Com+?
It really depends on how the com dll is being used. I'm assuming that you need to keep the classic asp application otherwise you'd rewrite the whole thing.
You don't want a webservice if the com dll is working with the session or http context of the site. I would move the com code over to a .NET Library Assembly, register it with interop (tlbimport/tlbexport) and use the interop assembly in your classic asp app to talk with the new .NET library.