Why use SOAP Toolkit for COM?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

LP - 15 May 2005 14:38 GMT

Hello,

I am looking into ways to consume Web Service (developed in .NET/C#) from
legacy COM based applications. Porting COM applications to .NET is not a
viable option at this time.
I am aware of SOAP Toolkit, but from what I am reading on msdn it's being
retired by microsoft in favor of .NET. My question is should I still spend
my time with SOAP Toolkit or just develop .NET assembly that consumes Web
Service and expose it as COM. I would think it'll be much slower than going
though SOAP Toolkit.
Anyone used SOAP Toolkit, any known issues with that? Please let me know
your opinion.

Thank you.

Reply to this Message

Chad Z. Hower aka Kudzu - 15 May 2005 14:58 GMT

> I am aware of SOAP Toolkit, but from what I am reading on msdn it's being
> retired by microsoft in favor of .NET. My question is should I still spend
> my time with SOAP Toolkit or just develop .NET assembly that consumes Web

IMO this is a no brainer - Use .NET to consume it and expose a COM interface.
And its not very often I will recommend VB over C#, but use VB.NET for this.
The COM support for C# is far inferior requiring a LOT more work. The VB.NET
not only has wizard support, but it supports easy changes while any changes
to your C# code will require you to muck around. This isa COM issue - not a
webservice one.

> Service and expose it as COM. I would think it'll be much slower than going
> though SOAP Toolkit.

It will add some slowness, but compared to the webservice the slowness is so
tiny you won't notice it.

--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"

Blog: http://blogs.atozed.com/kudzu

Reply to this Message

LP - 15 May 2005 16:56 GMT

Thanks for your comments Chud, That's what I've been thinking also. As far
as VB.NET vs. C#, it's not really up to me. As far as I know client uses C#
for all .NET development, and that's the language I have to use.

> The COM support for C# is far inferior requiring a LOT more work.

I think it's just really a matter of adding more attributes manually to
classes and functions in C#, while VB.NET comiler will insert them for you.
Other than that I don't think it's really that much work. Plus, I never
liked using wizard anyways.

>while any changes
> to your C# code will require you to muck around.

for example? I think setting binary compitablity will take care of that.

Thanks

> > I am aware of SOAP Toolkit, but from what I am reading on msdn it's being
> > retired by microsoft in favor of .NET. My question is should I still spend
[quoted text clipped - 18 lines]
>
> Blog: http://blogs.atozed.com/kudzu

Reply to this Message

Chad Z. Hower aka Kudzu - 17 May 2005 07:09 GMT

> I think it's just really a matter of adding more attributes manually to
> classes and functions in C#, while VB.NET comiler will insert them for
> Other than that I don't think it's really that much work. Plus, I never
> liked using wizard anyways.

Its not just the matter of the Wizard. I never used the Wizard in VB, and it
doesnt really do much. But making changes later are "instant" in VB. In C# we
had a lot of issues regarding changes to the COM object during development.
We did it in VB and it was cake. The VB in fact is just a COM wrapper around
our C# asm. :)

--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"

Blog: http://blogs.atozed.com/kudzu

Reply to this Message

Chinns Arumugam - 17 May 2005 00:28 GMT

I have the same issue, Still we are using classic ASP and COM components and we have to access a web service created using Soap Toolkit and our web server administration team is recommending us to use dotnet framework instead of Soap Toolkit.

Is there any place where I can find example code to develop .NET assembly that consumes WebService and expose it as COM.

Any help in this regard will be highly appreciated.

Reply to this Message

LP - 17 May 2005 02:35 GMT

http://msdn.microsoft.com/webservices/building/soaptk/default.aspx?pull=/library
/en-us/dnsoap/html/stkmigration.asp

> I have the same issue, Still we are using classic ASP and COM components and we have to access a web service created using Soap Toolkit and our web

server administration team is recommending us to use dotnet framework
instead of Soap Toolkit.

> Is there any place where I can find example code to develop .NET assembly that consumes WebService and expose it as COM.
>
> Any help in this regard will be highly appreciated.
>
> ---
> Posted using Wimdows.net Newsgroups - http://www.wimdows.net/newsgroups/

Reply to this Message

Chinns Arumugam - 18 May 2005 15:32 GMT

Thanks a Lot!, The above link was very helpful.

Reply to this Message

Why use SOAP Toolkit for COM?

Free Magazines