But as the download page states, this toolkit will be retired in April 2005.
This means Microsoft will no longer support its use. This would mean, for
example, that if a security bug were found in the toolkit after April 2005,
Microsoft would not be bound to correct it and issue a patch. Because of
this, most developers are not writing new code on the SOAP Toolkit.
Another option is to write a client of the webservice in C# (or VB.NET) and
have that *client* expose a COM interface. You would do this with tlmexp
and follow along the guidelines for COM--to-.NET interop. In this case the
ASP page would call the COM component, which would then act as the client to
the webservice. http://msdn.microsoft.com/library/en...perability.asp
A third option: If the webservice is simple, then you may be able to use
MSXML to make the call. Here is an example.
--
Dino Chiesa
Microsoft Developer Division
d i n o c h @ OmitThis . m i c r o s o f t . c o m
"Vincenzo Milazzo" <vincenzo.milaz zo@gmail.com> wrote in message
news:%23XWgerlz EHA.2788@TK2MSF TNGP15.phx.gbl. ..[color=blue]
> Ciao,
> come faccio a chiamare un webservice scritto in c# da una pagina asp in
> vbscript ?
>
> Ciao a tutti
>[/color]
Comment