Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Thu, 03 Aug 2006 10:00:00 GMT
Enterprise Library is a collection of application functionality blocks that you can re-use in your application for common functionality you'd otherwise have to write again and again. Here Jay Hilyard explains how to use them.
CLR Profiler - No Code Can Hide from the Profiling API in the .NET Framework 2.0
Tue, 14 Dec 2004 10:00:00 GMT
The common language runtime (CLR) profiling API makes available information about the application domains, assemblies, and classes that are loaded and used in a process, just-in-time (JIT) compiler notifications, memory usage tracking, tracing of events, exception tracking, managed to unmanaged code transitions, and the state of the runtime. And if that weren't enough, you will find a nicely enhanced profiling API in the .NET Framework 2.0. Find out what's coming up in this next version.
Design - Inspect and Optimize Your Program's Memory Usage with the .NET Profiler API
Tue, 17 Dec 2002 10:00:00 GMT
Developers using .NET often make memory leak tracking a low priority because the common language runtime takes care of garbage collection.What few developers realize, however, is that their objects' lifespans, along with their size and what other objects have been instantiated, all affect how they are cleaned up. Depending on the particular circumstances, these combinations can negatively affect performance, especially over the lifetime of an application. This article presents a way for developers to see memory usage and understand garbage collection using the .NET Profiler API.Along the way, a sample application to demonstrate these principles is built.