.NET news » Search results

monitor sql server processes and jobs, view executing sql query, kill process / job, object explorer, database shrink/log truncate/backup/detach/attach, object version control & compare

We've offered a few solutions for working with web cams within .NET to create fun and intriguing monitoring applications. In this article, we extend those ideas so that web cam images can be shared with multiple clients over the Web.

This is a windows based tool to continuous monitor your shared folder in network and generated a log for different folder.

The ATL COM Dll that captures requests from individual Webbrowser Control

You no longer have to rely solely on experience and code reviews to find code problems; FxCop can find many problems for you. It even lets you create and enforce custom rules that apply specifically to your organization's code.

Network Analyzer for Windows Mobile runs network utilities, for example ping and ipconfig, on a Windows Mobile powered device. Network Analyzer for Windows Mobile facilitates the troubleshooting of network connectivity issues. You can extend the harness. You can add user-defined tests (DLLs) to the list of tests to be executed. An xml input file defines the list of tests to execute. You can use Network Analyzer to send information about network traffic to a .cap file. You can then view the .cap file with the Network Monitor tool or the Ethereal tool.

This article demonstrates a quick and easy-to-use implementation for cross-AppDomain communication in .NET by leveraging Windows native messaging. The XDMessaging library is based on code developed to aid rapid development for a recent Vista project that required a lot of cross-AppDomain communication in a locked-down environment. It proved to be extremely useful in a number of scenarios where .NET Remoting would have been impractical, if not impossible, and actually solved more problems than I could have imagined due to its simplicity. The library is intended to send messages between multiple applications in a same-box scenario. For example, a task-tray application might want to communicate with or monitor a separate desktop application. The library does not implement cross-domain communication across a network, for which case .NET Remoting is sufficient.

The Health Monitoring system in ASP.NET 2.0 is designed to monitor the health of a running ASP.NET application in a production environment. It works by recording event information to a specified log source. The .NET 2.0 Framework includes a variety of built-in events that can be used by the Health Monitoring system, including events for monitoring application re-starts and stops, unhandled exceptions, and failed authentication attempts, among others. The .NET Framework also include support for logging these events to the Windows event log, to a Microsoft SQL Server database, via WMI, in an email, and to the ASP.NET page tracing system.

In this article we will continue our exploration of the built-in events and log sources. In particular, we will look at the WebFailureAuditEvent event, which is raised when there is a security audit failure. We will also look at the SimpleMailWebEventProvider event provider, which, as its name implies, sends event information via email.