Re: VB6 Client to VB.NET WebService
- Thanks Steve for your response. Yes, it is a legacy app that I am
enhancing, thus the VB6. The SOAP interface is strickly for inhouse-
intranet work and the SOAP server is a .NET webservice that I wrote
and maintain. I'm not implementing a huge SOAP library in the public
realm. I certainly understand your concerns.
In the meantime, I'm going to followup on your other suggestions and
see if I can make the MSSTK work.
--- In email@example.com, Steve Loughran <steve_l@i...>
> > Date: Thu, 26 Feb 2004 17:32:09 -0000
> > From: "Matt Janofsky" <mxjanofsky@u...>
> > Subject: VB6 Client to VB.NET WebService
> > I've created a .NET webservice that I'd like to access from VB6
> > clients. I've implemented a solution using Microsoft's SOAP
> > Toolkit. Unfortunately, it is practically impossible to
> > the SOAP toolkit. I'd like to write my own SOAP interface inVB6.
> > Does anyone know of any VB6 source code that can do the job? Ordoes
> > anyone have any suggestions? I've looked at PocketSOAP but Ithink
> > I'd rather do something myself. I'm trying to simply thewrite a
> > redistribution process.
> So lets see if I am getting this right.
> You want to simplify your distribution process, so you want to
> complete SOAP client that you can include with your VB6 app.Presumably,
> in VB itself?enough
> I would strongly encourage you not to do this. This is not a good
> reason to undertake the effort required to produce a functionalSOAP
> implementation, where functionality includes areas such as interop,failure
> section 5 encoding, correct mustUnderstand behaviour on headers,
> modes, etc, etc. Even the mainstream SOAP implementations have*issues*
> which are so fundamental they are terrifying. For example, theApache
> Axis self tests dont work on my machine when its clock is set toGMT
> -times sent to itself come up an hour out. Yet they work in the US.If
> that is the kind of intraop problem production code is having, homeon
> rolled stuff will be worse.
> If MSSTK is no good, spend more time with PocketSoap, or some money
> an installer. You can get an installer add on for the version ofvisual
> studio that comes w/ VB6 from somewhere on MSDN, I think, that canas
> incorporate .MSI files from third parties for better installation.
> ps, I wont even ask why VB6. I assume it is some legacy application
> issue and that you have not been overcome with the urge to use VB6
> the basis for new apps...