Our application is primarily VB6, however we are migrating toward .NET and a
newer architecture. For the time being though, we're stuck with a hybrid
approach with our ActiveX client application accessing .NET Web Services
provided by the new server-side application.

We like the benefits of Intellisense in the IDE. Visual Studio .NET will
provide Intellisense for a .NET client which references and accesses a Web
Service. Unfortunately though, the VB6 IDE doesn't recognize Web Services
natively. In order to address this we've developed the following paradigm
for any VB6 client which accesses a .NET Web Service:

ActiveX Client -> Interop -> .NET Broker Class -> .NET Web Service

By interposing a .NET broker class between the ActiveX client and the Web
Service, we achieve Intellisense at all application layers. However, the
overhead of the additional broker classes plus the need to deploy these for
Interop is starting to add up. Is there a better way of engineering

Active X Client -> .NET Web Service

in such a way that we'll see Intellisense whe nbinding to the Web Service
from within the VB6 IDE?

Thanks for your advice!

- Joe Geretz -