While it's great to see them going down the SOAP route, I was a little bit upset to see that they don't really define a schema for their results. The operations I looked at return big blobs of XML as xs:string. It would be nice to get some more visibility into those results...but some SOAP is definitely better than no SOAP at all :)

Some time ago I published ASP.NET user control that uses NOAA Web service. Dowloadable from here

http://blogs.msdn.com/mikhailarkhipov/archive/2004/08/12/213963.aspx

I'm having a heck of a time getting through our proxy server. To be more specific, this article (http://support.microsoft.com/Default.aspx?id=307220)seems to imply that it should "just work" because it should pick up the proxy settings from IE -- but it doesn't "just work". And I've tried, more or less, making an explicit proxy object as illustrated in (http://www.error-bank.com/microsoft.public.dotnet.general/114665_Thread.aspx) and have not been successful doing this either. And I tried editing my machine.config to point explicitly to our proxy server. No SOAP. (heh, heh)

Any suggestions?

I really hope you figured out your proxy issue. I can't get connected to the service using .net. It hang during NDFDgen. Any suggestions? Thanks.

Apparently NOAA WS broke some time ago. <br> <br><a target="_new" href="http://weblogs.asp.net/mikhailarkhipov/archive/2005/01/02/345516.aspx">http://weblogs.asp.net/mikhailarkhipov/archive/2005/01/02/345516.aspx</a> <br>

PingBack from http://mydebtconsolidator.info/story.php?id=14426