The trick I use for server-side debugging is to simply dump the contents to a file when retrieved. It's crude, but it gets the job done. Of course, that all depends on you having the source code for the server component and the permissions to rebuild and install a modified version on the server.
The second option would be to run your client side page through your debugger. Breakpoint it at that call and see what you get. If you don't get anything, then odds are the problem is on the server side. Of course, that "assumes" that you are calling it correctly! ...Glenn On Tue, Oct 21, 2008 at 9:42 AM, Brock <[EMAIL PROTECTED]> wrote: > > Sorry should have attached this to Joe Enos post... just pointing out > as he had questioned if this were a web page or a web service. The > below of course is the method found in my web service .asmx. I have a > web page .aspx that is consuming the data from the .asmx. my original > post had just the code behind and the html for the client page .aspx. > So I'm trying to figure out whether the failure to render is on the > client side or the service side. > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/DotNetDevelopment You may subscribe to group Feeds using a RSS Feed Reader to stay upto date using following url <a href="http://feeds.feedburner.com/DotNetDevelopment";> http://feeds.feedburner.com/DotNetDevelopment</a> -~----------~----~----~----~------~----~------~--~---
