The company I work for used to create web applications using an ASP
user interface, VB6 COM+ middle-tier with a SQL2K back-end. They have
recently moved on to .NET with ASP.NET user interfaces and a C# COM+
middle-tier. The .NET applications are being installed on the same
servers as the old applications and they are also using some of the
same VB6 COM+ objects (via Interop).
The problems we are having are as follows:
1) The web applications seem to require a local copy of the COM+
object in order to run. This means that whenever I recompile the COM+
object I need to copy it to the web server as well as the COM+ server,
which seems like unnecessary work.
2) Is there an easy way to use non .NET COM+ objects with a .NET web
application? At the moment we are referencing them using Interop which
works but seems to require that they are all copied locally.
Unfortunately this means that whenever a change is made to one of the
old COM+ objects I have to recompile and re-install all of our .NET
applications, otherwise the version they are looking for is different
to the one on the COM server. Does anyone know the correct way to use
VB6 COM+ objects with ASP.NET web applications?
3) We seem to need to export new application proxies for our .NET COM+
objects even when the interface hasn't changed, why is this?
Any help or advice would be appreciated.
Cheers