Soap Toolkit 3.0 | The Coffeehouse

surferdude
surferdude

I've got some questions and suggestions I'd appreciate feedback on from the MSFT folks. I've been reading up on the SOAP Toolkit 3.0 recently, and have found that it could work incredibly well for a project I'm currently working on. According to Rebecca Dias - Advanced Web Services Product Manager, Microsoft Corporation, the toolkit was primarily meant for "demonstration purposes". There have been a number of arguments as to why this does not appear to be the case, and also why the .NET framework is not the answer to some application requirements.

My reasoning for considering the toolkit rather than the .NET framework is identical to one of these arguments, specifically that the application I am developing must be a light weight download for 2K and XP. Our teams initial suggestion was that the application be done in C# using .NET, but this was immediately shot down by Marketing when they were told we might have to include the 24MB framework download, on top of the latest MSXML libraries.

So, maybe the folks there at MSFT can offer up some suggestions on how to accomplish SOAP development, without using .NET, and without using a discontinued toolkit meant for demonstration purposes only? Also, what are the chances MS might consider open sourcing the toolkit, so that the community can continue to develop and support it?

-surf

Keskos

surferdude wrote:
I've got some questions and suggestions I'd appreciate feedback on from the MSFT folks. I've been reading up on the SOAP Toolkit 3.0 recently, and have found that it could work incredibly well for a project I'm currently working on. According to Rebecca Dias - Advanced Web Services Product Manager, Microsoft Corporation, the toolkit was primarily meant for "demonstration purposes". There have been a number of arguments as to why this does not appear to be the case, and also why the .NET framework is not the answer to some application requirements.

My reasoning for considering the toolkit rather than the .NET framework is identical to one of these arguments, specifically that the application I am developing must be a light weight download for 2K and XP. Our teams initial suggestion was that the application be done in C# using .NET, but this was immediately shot down by Marketing when they were told we might have to include the 24MB framework download, on top of the latest MSXML libraries.

So, maybe the folks there at MSFT can offer up some suggestions on how to accomplish SOAP development, without using .NET, and without using a discontinued toolkit meant for demonstration purposes only? Also, what are the chances MS might consider open sourcing the toolkit, so that the community can continue to develop and support it?

-surf

Interesting question, but i would suggest you to check out the tech section (there is a forum for these type of tech questions here). Did you check out code project? Another option for you could be xml-rpc, in case you can't use SOAP.