VB6 Web Service? -- dotnet interop

pbd22
12/9/2007 9:52:13 PM

Hi.

I just got a project that is taking me into previously uncharted
territory.
I have a reasonably large VB6 project and need to "turn it into a web
service".
I know this isn't immediately possible. The two main options seem to
be:

1) convert the code to .NET and then create a web service.

I have heard that moving from VB6 to .NET for any significant project
is a major pain.

2) wrap the project in COM Interop which will act as a middleman
between a .NET project and the original VB6 project.

I am guessing #2 is the path of least resistance? I would really love
it if somebody
here could tell me if a) I am right that number 2 is a better way to
go and b) what is the best
way to go about implementing option 2? Has anybody here used a VB6
project and implemented it as a web service that is callable from
a .NET project?

Please help... new territory for me.

Johannes Passing
12/11/2007 9:30:50 AM

If your software is "reasonably large", 1) is indeed unlikely to be a
viable short-term solution and 2) sounds more promising. If your VB6
project is COM-based (or could be wrapped by a COM DLL), another option
might be to put it into COM+ and use the facilities provided by WCF for
COM+ integration (I have never tried that, but it seems to work). In
both of the latter cases, the degree of 'resistance' will most likely
depend on the complexity of your interfaces. For reasonably complex
interfaces, Interop (done manual or by WCF) can easily become a pain, too.

--Johannes

[quoted text, click to view]

--

dotnet interop : VB6 Web Service?