Hey Curtis, I totally feel you pain but have to admit that I kind of like to hear what you're saying about debugging web services. :-)
I work for Mindreef, Inc. and we specialize in web services debugging/diagnostic tools. We have a pretty rich history building debugging tools that started at NuMega Technologies (remember BoundsChecker and SoftICE?) and continue now in the Web Services world. You can grab SOAPscope 1.0 to do basic message capture but if you're interested I'd like to sign you up with our 2.0 beta program. We're *very* interested in hearing what folks like you have to say about building actual WS and how to debug them. We are gearing up for general release this fall and would love to have your comments. You can download the beta bits here: http://www.mindreef.com/beta/download.html The beta requires a license key at startup: 7m2g-qcfT-ah4m-//GS-N6hY-snf0-pG1j-bZgA Jim Murphy Mindreef, Inc. http://www.mindreef.com/ -----Original Message----- From: Moderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Curtis Koppang Sent: Friday, June 06, 2003 2:44 PM To: [EMAIL PROTECTED] Subject: [ADVANCED-DOTNET] Debugging ASP.NET WebServices I am currently getting an exception in a proxy I generated. This is the third issue I have stumbled upon; each of the previous issues was because of "invalid" WSDL or schema. Which leads me to a bigger question... Is it just me or does this architecture seem way to hard to debug? It seems like so much of the implementation is hidden from me its impossible for me to figure what I did wrong. So how do you debug this stuff? Is there a better (more low level) way to do this where I have to do a little more work, but I see more of the actual code? Are there any rigorous WSDL validators out there? I used the one built into XML Spy and it gives me the thumbs up on my WSDL/Schema. Any insight would be greatly appreciated, curt
