Franklin,
We have found that using the SOAP toolkit 2 makes it incredibly simple to
interop with webservices from legacy VB apps, no more than five minutes and
a few lines of code to get it up and running.
We've also used the XMLHttpRequest object from MSXML to call to web
services from within VB6 apps, which of course would require the MSXML
parser on the client, but some version comes with IE anyway. With HTTP
gets or posts to web services though, you'll run into parameter payload
size limitations very quickly (I think 2048k's the limit), but with SOAP
you don't.
Either way, you have simple and quick solution. Generating a CCW (COM
callable wrapper) from .NET would be the recommended technically correct
solution however, and we've begun migrating all our original iplementaions,
which were rolled out for the Beta releases of .NET.
Steve Holak
Senior Software Architect
Brokerage Concepts IS Dept.
610-491-4879
email: [EMAIL PROTECTED]
franklin gray
<franklin.w.gray@VITALTH To: [EMAIL PROTECTED]
OUGHT.COM> cc:
Sent by: dotnet Subject: [DOTNET] Com to DotNet
discussion
<[EMAIL PROTECTED]
COM>
04/11/2002 05:08 PM
Please respond to dotnet
discussion
I think this topic has already been discussed but the archives seem really
slow today.
I have an app written in vb 6.0 that our customers use. Can we make a
change to a vb 6 com dll to call a VB.net dll? If so, how hard is it? Do
I use interop?
What we are trying to do is have our existing app call a webservice.
You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
