Troubleshooting and Debugging Web Applications (16 percent)
- Configure debugging and custom errors
- ASP.NET Troubleshooting and debugging
- Debugging in Visual Studio
- Debugging preparation: ASP.NET Web Applications
- Enable debugging in ASP.NET
- Enable debugging on a remote server
- Debugging deployed applications
- Debug ASP.NET exceptions
- CustomErrors element
- CustomErrorsMode enumeration
- Error element
- Set up an environment to perform remote debugging
- How to set up remote debugging
- Enable debugging on a remote server
- Configuring IIS on Windows 2003 for debugging
- Debugging deployed applications
- Debug unhandled exceptions when using ASP.NET AJAX
- Client side script debugging
- Enable and start script debugging in IE
- Attaching to a script for debugging
- Debug script objects
- Implement tracing of a Web application
- ASP.NET Tracing Overview
- trace element
- View ASP.NET trace information with the Trace Viewer
- Enable tracing on ASP.NET application
- Enable tracing for ASP.NET page
- Tracing walkthrough
- Debug deployment issues
- ASP.NET IIS Registration Tool (Aspnet_regiis.exe)
- ASP.NET side by side
- Creating IIS Applications
- Monitor Web applications
- ASP.NET Health Monitoring overview
- System.Web.Management
- Implement custom Health Monitoring events
- Performance overview
- Performance counters for ASP.NET
- View ASP.NET performance counters how to
- Monitoring ASP.NET performance
- The customErrors element provides information about custom error messages for ASP.NET applications. The mode attribute of the customErrors element specifies whether custom errors are enabled, disabled, or shown only to remote clients.
- The mode attribute of the customErrors element specifies whether custom errors are enabled, disabled, or shown only to remote clients. Setting this attribute to RemoteOnly specifies that the custom errors are shown only to remote clients.
- Use the attribute in the Web.config file of the application to deny access to a resource. The users attribute of the element specifies the user names that are denied access to a resource.
- Use the customErrors element to provide information about custom error messages for an ASP.NET application. The mode attribute of the customErrors element specifies whether custom errors are enabled, disabled, or shown only to remote clients.
- Use the customErrors element to provide information about custom error messages for ASP.NET applications. The mode attribute of the customErrors element specifies whether custom errors are enabled, disabled, or shown only to remote clients.
- A user required necessary permission for remote debugging on a remote computer.
- The wwp.exe process is associated with application pools in IIS. If a user has more than one application pool, he will run more than one instance of the wwp.exe process running.
- The IScriptControl interface is used to represent methods that ASP.NET server controls have to implement to depict ECMAScript (JavaScript) resources in AJAX enabled applications.
- Trace.axd is an Http Handler that can be used to view the trace details for an application. It is resides in the application’s root directory.
- The healthMonitoring element is an ASP.NET Settings Schema. It is used to configure an application for health monitoring. It consists of attributes, child elements, and parent elements.
- The trace element is an ASP.NET Settings Schema. It is used to configure the ASP.NET code tracing service that controls how trace results are assembled, stored, and displayed.
- The element of the Web.config file provides information about custom error messages for ASP.NET applications. The mode attribute of the element is used to specify whether custom errors are enabled, disabled, or shown only to remote clients.
- The pages element is an ASP.NET Settings Schema. It is used to define page specific configuration settings globally.
- The Duration attribute of the @ OutputCache directive specifies the amount of time (in seconds) for which a control is cached. The VaryByParam attribute allows developers to vary the output cache depending on a GET query string or form POST parameters.
- The ErrorPage attribute of the @ Page directive is used to set the URL if an unhandled exception occurs. Sam can set this target to the home page.
- The TraceMode attribute of the @ Page directive specifies the order in which the trace information is to be displayed. It can be sorted either by the Category column (SortByCategory) or by time column (SortByTime).
- Tracing can be enabled for an application by using the trace element. The settings of the Web.config file overrides the settings of the Machine.config file.
- The AutoPostBack property works properly only if a browser is set to allow scripting. By default, a browser is set to allow scripting, but some users disable it for security reasons.
- Tracing can be enabled or disabled for a page by using the Trace attribute of the @ Page directive.
- Tracing can be enabled for an application by using the trace element in the application’s Web.config file.
- The enabled attribute of the trace element specifies whether or not tracing is enabled for an application. By default, this attribute is set to false. Setting this attribute to true will enable tracing for the entire application.
- Smart navigation is best used with ASP.NET pages that require frequent postbacks.
- The EnableEventValidation attribute of the @ Page directive is used to validate .aspx page events in postback requests and callback scenarios.
- The EnableViewState attribute of the @ Page directive is set to true, which indicates that the view state is maintained across page requests.
- The pageOutput attribute specifies whether or not trace output is rendered at the end of each page of an application.
- The requestLimit attribute specifies the number of trace requests to be stored on the server. The trace is automatically disabled if the limit is reached.
- Add a Page directive to the Page.aspx in order to make it work properly.
- A new IIS application can be created for hosting WCF services. Alternatively, a WCF service can be deployed into an existing ASP.NET application. Before deploying a WCF service implementation to the IIS or ASP.NET application, you must create a .svc file for the WCF service. Only then, the WCF service can be configured.
- Web applications run inside a worker process that is assigned to an application pool. If the application pool is not started yet, the worker process does not run for that application pool.
- Use Windows System Monitor to identify spikes inside a component and to get notification if the average time to process messages reaches a certain level.
- Use System Monitor and Microsoft Operations Manager to collect information from the custom performance counters inside a component when the component is running on a production server.
- Profiling and instrument application components are the best options to improve the application performance when the application is consuming lots of memory resulting in slow operation.
- The system.web element is an ASP.NET Settings Schema. It is used to specify the root element for the ASP.NET configuration section and contains configuration elements.
- The compilation Element is an ASP.NET Settings Schema. It is used to configure all compilation settings that ASP.NET utilizes to compile applications. In .NET Framework, the compilers child element of the compilation element is deprecated in support of the compilers element of the system.codeDom section.
- Windows Management Instrumentation (WMI) is a set of extensions to the Windows Driver Model that provides an operating system interface through which instrumented components provide information and notification.
- Enable tracing for a page when the page has been deployed to a remote server to view execution time of page events.
- The performance counter mechanism is used to monitor the performance of all the Web applications during the execution period.
Recent Comments