.NET news » Debug

The article is regarding a new feature in Visual Studio .NET 2005, that gives you the ability to decide how your image data is to be visualized in debug time.

Just ran across the App Verifier that now supports Windows Mobile 5

http://www.microsoft.com/downloads/details.aspx?FamilyID=d275348a-d937-4d88-ae25-28702c78748d&displaylang=en

If you aren't familiar the Application Verifier tool assesses the stability of an application and detects common programming mistakes. The tool can detect and pinpoint memory leaks, handle leaks, and leaks in graphics device interface (GDI) objects.

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.

Analysis Management Objects (AMO) for SQL Server 2005 facilitates client-side custom programming as Decision Support Objects (DSO), the object model in SQL Server 2000 Analysis Services. With AMO, a whole range of data mining questions can be answered at the operational level. This means that sales and marketing departments get answers more quickly and thus can make informed decisions.

In theory the .NET debugging API is simple and a joy to use, but there is a lack of a detailed overview as to how to use it in the framework SDK. In this article, we'll cover how to write a debugger under .NET, and will also touch on the profiling API support.