At Mindreef, we work with many different SOAP implementations. That's why we made sure SOAPscope™ is toolkit-independent. Some of us eschew toolkits, and code our own SOAP. Some prefer Java-based tools, and others use Microsoft .NET. Our student intern, Kevin, insists that Perl and SOAP::Lite are the only way to go. Unfortunately, mixing toolkits doesn't always work out the way you planned.

Recently I participated in a newsgroup thread on debugging ASP.NET and I advocated using the GUI Debugger standalone debugger when you don't have VS.NET or just don't want to fire up VS.NET to run a debug against one or more ASP.NET pages. This is especially handy when you use editors such as Web Matrix and other basic text editors instead of coughing up the $$$ to license and use VS.NET. AS I found myself going into a kinda long explanation of how to use GUI Debugger with ASP.NET, I decided to just post this brief tutorial for everyone to access in the future.

One of the most challenging aspects of Active Server Pages (ASP) development prior to .NET was debugging and tracing. Setting up interactive debugging in Visual InterDev was nontrivial, and getting a quick trace of the application at run time required you to resort to Response.Write statements. With .NET comes a new way to debug your ASP.NET applications: built-in trace functionality. In this column, I'll cover the TraceContext class, walk through a code example using Visual Studio .NET, and show you how to make the most of the trace output.

XML Web services are touted by Microsoft as the next big thing. But until recently, developers were hampered in their efforts to effectively develop them, placing the future of the new protocol in some doubt. Fortunately, Visual Studio .NET has made the development and consumption of Web services almost trivial, while making it possible—if not always simple—to debug them.

Using BERT Lite on EraServer.NET, you can collect valuable debugging information during the testing phase of your ASP.NET application. You can also track changes between builds and send change reports via email. BERT stands for Bug and Enhancement Request Tracking.

Using BERT Lite on EraServer.NET, you can collect valuable debugging information during the testing phase of your ASP.NET application. You can also

Visual Basic provides many tools to help analyze how your code operates. These debugging tools are particularly useful in locating the source of errors, or bugs. You can also use them to help you learn how code written by other people works. When you write your code, you will never be able to create code that works first time round perfectly. Or if you do, if you change another section of code, this may well affect code you have already written which then does not work.

This step-by-step article describes how to set up multiple-user debugging of Microsoft Visual Studio .NET applications in semi-isolated mode under Internet Information Services (IIS) version 6.0.

This article provides a list of articles that describe some of the most common problems you encounter when you debug ASP.NET applications in Visual Studio .NET.

Developers who make regular use of the VB debugging tools will be in for a shock - there are virtually none for ASP! On your local server, you usually receive a 505 error when there is a scripting error, along with the error description and line number that it occured on.... and that is just about it. If you have a custom 505 error page, you won't even be able to get that.

When you debug ASP.NET programs in Visual Studio .NET after you install the Microsoft Security Toolkit, you receive the following error message:

The purpose of this article is to outline our server debug process from one very general server symptom: Server ”II” would stop responding to external requests.

In this article we will review these classes and see how to use them. Although we specifically target Web applications in this article most of all that we will discuss applies to other programming models (like standalone programs) too. For now, we will focus on debugging and tracing. The code examples in this article will use C# but the ideas are language independent and can be used in any language that can be used to program in .NET framework.

Although VS.NET is a far superior tool for debugging your ASP.NET applications, there still are some powerful tools built into ASP.NET that you can utilize even when using a tool like Notepad.

So, what should you do if you attempt to start debugging a Web application and get the dreaded "Unable to start debugging on the Web Server" error? Here's your one-stop checklist...

Although VS.NET is a far superior tool for debugging your ASP.NET applications, there still are some powerful tools built into ASP.NET that you can utilize even when using a tool like Notepad.

The .NET framework comes with an enhanced library to aid in debugging and performance monitoring.Before web development was popular and most applications were stand alone programs debugging strategies depended a lot on how and where these were being developed. When developing in C/C++ printf(...) was a favorite debugging tool on both UNIX and DOS environments for programmers. That changed when Integrated Development Environments - IDEs - like Borland's (now Inprise) Turbo C++ and Microsoft's Visual Studio came along.

Debugging ASP.NET concentrates on debugging issues related to Microsoft’s new web development platform, ASP.NET. This article explains the Visual Studio .NET Debugging Environment in detail.

Describes debugging ASP.NET Web services. Information includes: debugging a Web service on //localhost, debugging a Web service on a remote server, and debugging a deployed Web service.

But debugging JavaScript code can be a pain, unless you know a few tricks. ASP.NET has many advantages over classic ASP in the area of debugging.