| An Exception to the Rule, Part 2 |
| MSDN |
| In the previous column, we briefly mentioned Application_Error events and Page_Error events. These events are raised whenever we have an unhandled exception occur within our application. If a Page_Error event is present within an ASP .NET page, and an unhandled error occurs, the event is raised. Application_Error is slightly different. It is raised for all unhandled exceptions in our ASP .NET application and is implemented in global.asax or within an HTTP Module. |
|
| Best Practices for Using DTS for Business Intelligence Solutions |
| MSDN |
| Discover the best practices for using Data Transformation Services (DTS) within the Data Warehousing Framework to capture and present data as Business Intelligence solutions. |
|
| C#: A Message Queuing Service Application |
| MSDN |
| This article outlines a Windows service solution designed to process several message queues, focusing on the application of the Microsoft .NET Framework and C#. |
|
| Custom Error Pages and Logging Errors |
| DevHood |
| When building any application, be it a web application or a desktop application, handling errors gracefully is essential. Users don't want to see a stack dump or what line of code the application crashed at. This is why we provide custom error pages for users. This also gives us a method of tracking errors that users cause. This tutorial will give you an overview on how custom error handling is done. It will also provide you with some code which you can use to create your own custom error pages for your web applications.
|
|
| Custom Errors in ASP.NET |
| .NET Xtreme |
| When a runtime or design-time error occurs in an application, ASP.Net shows a default error page that gives a brief description of the error along with the line number on which the error occurred. A developer would wish to view this default error page, during the testing of the application since the description helps him in rectifying the error. But he would never want a user trying to access his application, to view this error page. The user would be least bothered to know about the error. Instead of showing the default error page, it would be more sensible to show a customized error page that would let the user send notification of the error to the administrator. |
|
| Custom Errors in ASP.NET |
| DotNetJunkies |
| Structured exception handling is a fundamental part of the CLR and provides .NET programmers a great way of managing errors. In addition to CLR exception system, Amit explains how ASP.NET also provides ways of handling errors. |
|
| Exception Management in .NET |
| MSDN |
| This document discusses design and implementation guidelines for exception management systems that use .NET technologies. It focuses on the process of handling exceptions within .NET applications in a highly maintainable and supportable manner. |
|
| Global Exception Handling with ASP.NET |
| http://webdeveloper.earthweb.com/ |
| You can't debug a problem if you don't know that it exists. After you take your web application live, you are no longer the only one who is using it (hopefully), so you need an effective plan to track exceptions when they occur while others are surfing your site. A great way to do this is to implement an exception handler at the application level. This will allow you to consolidate the logging and notification parts of your exception handling in one convenient place. As you'll see from the code examples that follow, your global exception handler can handle both specific exceptions that you trap in your code and generic unhandled exceptions. |
|
| Global Web Application Level Error Reporting |
| Master C# |
| As a web master of any web site it becomes of primary importance for you to know of any error that occurs in your Web Application. Even though good design practice calls for Error Handling within the application itself, still there could many un-handled errors and exceptions occurring within your web applications spoiling your clients experience. |
|
| How To Host .NET Remoting Objects In Windows Service |
| The Code Project |
| For sometime I have been working on Remoting projects using .NET but every time I will always end up creating a console application to run as a remote server and host the remoting object in that. This definitely is not going to be case in real world applications. Most of the time you will require that your remote object is hosted in a server that is running all the time and does not require any user intervention like in Console application. |
|
| Instrumentation: Powerful Instrumentation Options in .NET Let You Build Manageable Apps with Confidence |
| MSDN |
| Take a look at the various instrumentation technologies available in the .NET Framework, such as tracing, logging, WMI, and EIF, that will help you measure your apps. |
|
| Logging Unhandled Page Exceptions To The System Event Log |
| DotNetJunkies |
| Error handling is a critical part of building enterprise level web applications,
for that matter, it is a huge page of any application. In one of last weeks article we discussed using the
Try...Catch...Finally statement to catch and respond to exceptions thrown during the page execution process.
In this article I will be introducing a new way to catch Page-Level exceptions by introducing the HandleError Method. |
|
| Manipulating the Windows 2000 Registry and Event Viewer Using C# |
| C#Today |
| The Windows Operating System provides a lot of flexibility for programming against the various services offered by it. We can develop applications to manipulate the OSs various services like the registry and EventViewer. In this article, Sandra Gopikrishna focuses on the following topics - writing to and reading from the system registry by employing the classes of the Microsoft.Win32 namespace, and interacting with the Windows 2000 event logs such as the application, security and system logs by employing the classes of the System.Diagnostics namespace. |
|
| Many Parties Observing a Long Process |
| DotNetJunkies |
| Sometimes it is required to start some lengthy process and allow all interested parties to observe execution of that process. Filip uses a simple example of a lotto draw to show how to make this possible. |
|
| Monitoring Processes and Threads in .NET |
| C#Today |
| In this article, Melanie Talmadge shows us how to write a process and thread monitoring system in .NET using C#. We cover the System.Diagnostics namespace with its Process and ProcessThread classes for working with process and threads, and write our own Task Manager application, similar to that which comes with Windows NT and Windows 2000. This program displays all the running processes, their related resources and related threads. |
|
| Online CPU Console using a Web Control Library with .NET Security |
| C#Today |
| Administering applications and servers when not connected to the network can be a nightmare, especially when only a few people manage the application. Just imagine going out for an evening on the town and then you’re paged at one o’clock in the morning with an alarming message that your application has gone down. For companies without Virtual Private Networks (VPN) the task is even more difficult because now you must come to the office to rescue your application. |
|
| PRB: "Requested Registry Access Is Not Allowed" Error Message When ASP.NET Application Tries to Write New EventSource in the EventLog |
| http://www.kbalertz.com/ |
| (329291) - When you use ASP.NET to create a new event source in the event log, you may receive the following error message: System.Security.SecurityException: Requested registry access is not allowed. |
|
| System.Management Lets You Take Advantage of WMI APIs within Managed Code |
| MSDN |
| Visual Studio .NET and the Microsoft .NET Framework SDK provide a new set of APIs and tools that let you consume Windows Management Instrumentation (WMI) data and events from managed .NET applications. After presenting an overview of what's new for WMI in the .NET Framework and the Visual Studio .NET environment, the author provides an in-depth exploration of the Management Extensions in Visual Studio .NET for Server Explorer. These extensions help you develop management-aware software and come in handy in a variety of distributed application development scenarios. |
|
| Top 10 tips and tricks to code professional looking .NET apps |
| The Code Project |
| Top 10 tips and tricks to make your little C# app look professional… things like interacting with Windows registry or Event log, ensuring a single instance of an app, sending emails, creating useful (and techie looking) logs of operations, getting IP addresses from host names and other cool stuff ! |
|
| Top 10 tips and tricks to code professional looking .NET apps |
| The Code Project |
| Top 10 tips and tricks to make your little C# app look professional… things like interacting with Windows registry or Event log, ensuring a single instance of an app, sending emails, creating useful (and techie looking) logs of operations, getting IP addresses from host names, and other cool stuff! |
|
| Wicked Code: Foiling Session Hijacking Attempts |
| MSDN |
| Don't let hackers get your session state data |
|
| Windows Service State Publisher |
| The Code Project |
| Monitor Windows Services for changes in state using well known design patterns |
|
| Windows Services: New Base Classes in .NET Make Writing a Windows Service Easy |
| MSDN |
| Windows services are applications that run outside of any particular user context in Windows NT, Windows 2000, or Windows XP. The creation of services used to require expert coding skills and generally required C or C++. Visual Studio .NET now makes it easy for you to create a Windows service, whether you're writing code in C++, C#, or Visual Basic. You can also write a Windows service in any other language that targets the common language runtime. This article walks you through the creation of a useful Windows service, then demonstrates how to install, test, and debug the service. |
|
| Writing Managed Applications for the .NET Framework |
| MSDN |
| The purpose of this article and sample is to demonstrate how Visual C++ can be used to incorporate the .NET Framework into C++ applications. |
|
