G
Guest
Hi guys,
I would like to create a .NET 2005 DLL (class) that could be referenced
localy thru COM interop, and as a WebService. With other words my web
application needs this DLL (directly referenced), my legacy application needs
to access it thru COM (for integration purposes), and remote clients will
need to call the same DLL functions using Web Service interface.
I know it could be done with wrappers, but that is far too time consuming.
So, is there an alternative way of developing only one DLL that can serve all
three kinds of clients?
Regards,
Alex
I would like to create a .NET 2005 DLL (class) that could be referenced
localy thru COM interop, and as a WebService. With other words my web
application needs this DLL (directly referenced), my legacy application needs
to access it thru COM (for integration purposes), and remote clients will
need to call the same DLL functions using Web Service interface.
I know it could be done with wrappers, but that is far too time consuming.
So, is there an alternative way of developing only one DLL that can serve all
three kinds of clients?
Regards,
Alex