How to: Start a Debugging Session
This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.
Use the Voice Response Debugging Window dialog box to debug speech applications.
Starting a Debugging Session
To start debugging a managed code voice response application
In Microsoft Visual Studio 2005, press F5.
In the Voice ResponseDebugging Window dialog box, click Call.
To start debugging a SALT voice response application or VoiceXML application
On the Debug menu, point to Windows, and then click Voice ResponseDebugging Window.
In the Voice ResponseDebugging Window dialog box, click Call.
Note
When debugging a Speech Application Language Tags (SALT) voice response application that uses a SIP peer other than the Voice Response Debugging Window dialog box, changes to .js or .pf files included in the application might be rejected. The rejection occurs because resource files such as .js and .pf files are downloaded using HTTP and cached according to the Web server cachability settings. As a result, changes to those files might not be reflected until the expiration time occurs. The workaround for this problem is to open a command prompt and type sc control mss 131. This command forces Speech Server to reload all resources, including .js and .pf files.
See Also
Other Resources
How to: Manually Start a New Event Tracing Log
Debug Speech Applications
Use Speech Server Tools to Develop Voice Response Application Components
Speech Server Tutorials
Walkthroughs for Managed Code Voice Response Applications