470,849 Members | 1,071 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 470,849 developers. It's quick & easy.

Calling a .net Webservice from classic ASP

Currently I use the MS Soap Toolkit to expose some 20 or so com objects
for use by classic asp pages, this has to be replaced as support is
ending.
I have found two proposed solutions below and would appreciate any
comments, particularly from somone who has done this before.

Create a .net WS to expose the Com Objects
From searching the web it looks like a couple of options are available

to access the web service from classic asp:

1 Access the WS using the MSXML http component to create headers
ASP > MSXML > . net WS > COM ( interop)
This requires writing a lot of code, I've read also that the error
handling is difficult. Basically it sounds like writing soap toolkit
again in ASP.

2 Using .net create a .net assembly to call the WS using the .net ws
methods, expose this to the ASP page using a COM callable wrapper.
ASP > CCW ( interop) > .net Assembly > . net WS > COM ( interop)
In terms of stability this looks much better as the .net ws methods
will handle errors much better. Also it should be possible to design
the component in such a way as to minimise the amount of code to write.
However there is a lot of interop involved and I'm concerned about the
overhead involved.

Can anyone give me some pointers?

Mar 29 '06 #1
1 1933
Not sure you still need this, but I wrote a COM class that uses the MS SOAP
SDK and it has been used in a production environment for a couple of years so
it seems to be stable. I used it to call a .NET web service from a classic
ASP web application.

I believe I still have the code somewhere. Do you still need this?

"AnRonMor" wrote:
Currently I use the MS Soap Toolkit to expose some 20 or so com objects
for use by classic asp pages, this has to be replaced as support is
ending.
I have found two proposed solutions below and would appreciate any
comments, particularly from somone who has done this before.

Create a .net WS to expose the Com Objects
From searching the web it looks like a couple of options are available

to access the web service from classic asp:

1 Access the WS using the MSXML http component to create headers
ASP > MSXML > . net WS > COM ( interop)
This requires writing a lot of code, I've read also that the error
handling is difficult. Basically it sounds like writing soap toolkit
again in ASP.

2 Using .net create a .net assembly to call the WS using the .net ws
methods, expose this to the ASP page using a COM callable wrapper.
ASP > CCW ( interop) > .net Assembly > . net WS > COM ( interop)
In terms of stability this looks much better as the .net ws methods
will handle errors much better. Also it should be possible to design
the component in such a way as to minimise the amount of code to write.
However there is a lot of interop involved and I'm concerned about the
overhead involved.

Can anyone give me some pointers?

Apr 8 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

4 posts views Thread by Julian Hershel | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.