.NET news » Bugs

BugSentry is Fire and Forget bug tracking for .NET. From the FAQ... How do I use BugSentry? * Install the BugSentry Client and generate a key pair. * Add a reference to the BugSentry Library to your project. * Create an instance of BugSentry, using your public key. * Call BugSentry from your error handlers. * Bug Sentry handles the rest. How can BugSentry help us write better code? No user in history has ever submitted a complete and accurate bug report. Bug Sentry makes sure you know about every glitch and bug without relying on users. How is this better than just logging the bugs manually? You can still log bugs in using the BugSentry interface, but BugSentry makes sure you get issue reports for the bugs your testers missed. You also get issue reports after the application is in production.

While implementing Client Script Call Back, you may receive the error "The target '__Page' for the callback could not be found or did not implement ICallbackEventHandler." This article discusses on the same.

This tip outlines further tricks to resolve or work around this common bug.

You may receive the error "Error while trying to run project: Unable to start debugging on the web server. You do not have permission to debug the application. The URL for this project is in the Internet zone. Click Help for more information." This article discusses on the resolution for the same.

Reliability requires the capacity to execute a sequence of operations in a deterministic way, even under exceptional conditions. This allows you to ensure that resources are not leaked and that you can maintain state consistency without relying on application domain unloading (or worse, process restarts) to fix any corrupted state. Unfortunately, in the.NET Framework, not all exceptions are deterministic and synchronous, which makes it difficult to write code that is always deterministic in its ability to execute a predetermined sequence of operations. In this article Stephen Toub will show you why, and explore features of the .NET Framework 2.0 that help you to mitigate these situations and write more reliable code.

Security Briefs: Credentials and Delegation

Errors happen. But in production, error logs often provide little or no help in pinpointing the exact line of code in which the problem originates. You can't usually isolate the root cause by modifying code in a production environment because recreating the exact same environment is very difficult due to the large number of potential software and hardware configurations. This article provides some concrete steps you can take to get at the heart of the problems in your production code.