How to debug a Windows Azure application

Windows Azure is a Silverlight based software, and its development portal is now a new one. All of its information, all operations can be done in one page. Use this new portal, from configuring the guest operating system to stopping or restarting a service, almost on one page, to get everything done. The following is a brief introduction to Windows Azure application Debugging

Debugging an application is common, allowing developers to track and fix existing problems and ensure that applications are more reliable and efficient, so the ability to debug an application is important to developers .

Microsoft Windows Azure developers need to use the debugger during program development and running in the cloud, and during coding, developers can debug their code using the Azure Emulator and Visual Studio, and when the program is running in the cloud, They can perform diagnostic logging programs that provide information about the execution of the application and provide an auxiliary role for application tuning.

Toolbox: Visual Studio and Azure SDK

Before you debug a Microsoft Windows Azure application, you need to install the visual Studio 2010 and Microsoft Azure SDK, and if you don't have a paid version of VS 2010, you can get from here (http:// www.microsoft.com/express/Web/) Download the free visual Web Developer Express.

debugging practices during Azure application coding

If you debug Windows Azure applications during coding, you can use the simulator to display the simulator, you need to start debugging the application, if you do not have an azure application, you can get from here (http://www.developer.com/imagesvr _ce/2819/myfirstazureproject.zip) Download a demo program, and then start Visual Studio for debugging. Right-click on the System tray icon and select "Compute Emulator" * "Show Compute emulator UI" to start the simulator as shown in the following figure.

1 Start simulator
The Windows Azure Emulator window opens, as shown in the following illustration:

2 Emulator main Window
You can click on the role to view log information for the record, as shown in the following figure:

3 View log Information

If you click on the right node, you can see all of your custom traces, debugging the Windows Azure application experience and debugging the ASP.net application or Web service is similar. Using IntelliTrace to debug hosted Windows Azure applications, if you want to debug cloud applications in a production environment, you can use the IntelliTrace feature (only the visual Studio 64-bit version has this feature, and windows Azure applications are built with. NET 4.0.

4 Windows Azure Application deployment options

In the figure above (right-click on the item and choose Publish to open the window), you need to make sure that the check box before "Open IntelliTrace for. NET 4 Roles" is selected. If you click on the "Settings" link next to it, you can open the Advanced Configuration window, such as collecting only events or collecting events and invocation information at the same time.

5 IntelliTrace settings (General Options)
In addition, you can set up the collection of IntelliTrace event types.

6 IntelliTrace Settings (IntelliTrace event option)
The default size of the log file is only 250GB, if you plan to log verbose logs (in a loop buffer), set the log size in the Advanced tab window.

7 IntelliTrace settings (Advanced options)
When you publish an application that opens IntelliTrace, you can download your log by connecting to the Azure compute instance from Visual Studio's Server Explorer window.