Regular expression started in Perl language. But it is now used everywhere: text editors, programming languages, and software testing tools. Regular expression is powerful, but hard to learn. This page allows you to learn and test regular expression with your own strings, match patterns, sub patterns, and modifiers.

Altova® XMLSpy® includes a powerful XSLT 1.0/2.0 debugger for troubleshooting and perfecting XSLT 1.0 and 2.0 stylesheets. Testing and perfecting XSLT stylesheets can be a complicated, time-consuming process. With the XMLSpy XSLT debugger, you can step through and debug even the most intricate stylesheets quickly and easily. XMLSpy includes a complete implementation of the powerful new XSLT 2.0 and XPath 2.0 specifications, and the XSLT debugger allows you to debug both XSLT 1.0 and 2.0 stylesheets.

The Altova® XMLSpy® XQuery debugger allows you to test and perfect your XQuery code as you’re writing it. You can set breakpoints on any expression in the XQuery document and any node(s) in the associated XML file to halt the debugger whenever that particular instruction or node is accessed. This provides you with an immediate visual understanding of the way that your XQuery document is processing the XML data.

This tutorial covers: steps for debugging XSLT stylesheets, using breakpoints, viewing processing information, determining which template generated particular XML output, determining the output generated by a particular XSLT template, profiling XSLT stylesheets handling parser and processor errors, and debugging java files in conjunction with XSLT.

An overview of the Stylus Studio XQuery Debugger that alows you to set breakpoints and step through the evaluation of any XQuery expression in a way that gives you complete control and visibility into the XQuery expression evaluation process.

An overview of the Stylus Studio XSLT debugger, helpful for building bug-free XSLT stylesheets and XML data transformation applications. The XSLT debugger gives you visibility and control over the XSLT transformation process, and supports cross-XSLT-processor (MSXML, Saxon, Xalan, System.XML, etc) , and cross-language XSLT debugging (Java XSLT extension functions, etc).

Because the interaction of a style sheet with a data file can be complex, and style sheet errors are not always obvious, this section provides troubleshooting advice for the style sheet author.

When your XSLT stylesheet doesn't do exactly what you want it to and you don't know why, what resources are available to figure it out? In other words, how do you debug a buggy stylesheet?

Developing code is difficult, developing code that works is even more difficult! You need techniques to debug your application.

Before describing the Visual Studio .Net T-SQL Debugger, let's start by discussing its predecessor, the SQL Server T-SQL Debugger. While developers are accustomed to using the SQL Server T-SQL Debugger to debug stored procedures, most do not realize they can debug user-defined functions as well. After all, if you select the user-defined function in the Object Browser and then right click, the Debug option is grayed out.

This session described a full range of techniques for effective debugging under .NET. Most of them were the plain and practical explanations of features that the CLR tools and Visual Studio.NET provide natively.

Recently I was moving along with my ASP .NET Web site de-sign and was quite pleased to see just how much easier ASP .NET made the whole process. Being a good boy, I went through the design process and was about to start development when I noticed a small problem.

The Debug.Assert is one of the greatest tools for developers to use for creating solid, bug free code. The problem with using Debug.Assert lies when you are writing an ASP.Net web site or Web Service. By default with these types of projects, when an Assertion fails, Visual Studio will log the Assertion message to the Debut Output window. But thats it, no other type of notification that the Assertion failed. ASP.Net and Web Services do not have any built in ability to break into debug mode when an Assertion fails. This sample creates a dll that once referenced by your ASP.Net or Web Service app, just adding a small block of xml into your web.config file will cause the debugger to automatically break into your code.

In general, debugging a .NET Framework application by running it inside DbgClr requires several steps. Before running the debugging sample, you must first compile the application and its components. If you would like to stop execution at a particular statement, you should perform the following five steps.

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.

The Microsoft® .NET Framework comes with a rich set of programming tools for debugging and tracing applications. I'm not talking about integrated debuggers; I'm referring to software components that you use in the development cycle. Debuggers are a different animal because they are interactive tools that normally integrate with a full-fledged IDE such as Visual Studio® .NET.

One of the nicest parts of ASP.net debugging is what I call post-mortem debugging. Lets observe what a typical post-mortem trace looks like on my server need vb Speech SDK example or help. Passing Photograpgh at runtime.

Visual Studio .NET makes developing Web services applications relatively easy, but debugging them is a different story. Learn how to debug your Web service apps using VS.NET. Examples

For our purposes I elected to use a NUnit assembly and NUnit to demonstrate debugging a hosted process.