|
|
browse.develop.com
Browse.develop.com is a community that was established to collect and
organize valuable web information. Our technical staff have selected and
indexed information and courses that they feel will help you stay
current on best practices across the SDLC.
|
2 Articles match "ASP.Net","WinDBG"
|
Related DevelopMentor Courses
|
MORE
|
|
.NET Programming for Performance
NET applications Scale your application to multicore machines using threads Improve memory usage through proper understanding of assemblies, types, and JIT compilation Debug difficult problems using WinDBG, SOS, and ADPLUS Effective .NET Real-world problems can't always be solved by running in the Visual Studio debugger, so you will practice getting memory dumps from live systems and see how to use Visual Studio in concert with tools like WinDBG, SOS, and Performance Monitor to ferret out problems like memory leaks, deadlocks, and runaway threads. Write code that works well with the garbage collector Properly handle and throw exceptions Automate transactions with System.Transaction Implement IDisposable to build reliable .NET
DevelopMentor Courses
- Friday, June 12, 2009
Guerrilla .NET
idioms like iterator methods, the lambda operator, and extension methods Write code that works well with the garbage collector Handle and throw exceptions properly Work with Windows Presentation Foundation (WPF) and XAML Write browser applications using Silverlight Manage long-running processes with Windows Workflow Foundation (WF) Threading and Concurrency Scale your application to multicore machines using threads Debug difficult problems using WinDBG, SOS, and ADPLUS Understand how the .NET present up to the minute updates on topics like Windows Azure architecture and storage, ASP.NET
DevelopMentor Courses
- Friday, June 12, 2009
|
2 Articles match "ASP.Net","WinDBG"
|
The Latest from DevelopMentor
|
MORE
|
|
SOS: finding the method bound to an EventHandler with WinDbg.
My prepared application was an ASP.NET application that would leak memory by holding references to the page objects after they had completed their work. then loaded this dump up into WinDBG and started poking around.
First, VS.NET, so you need to familiarize yourself with WinDBG to do this.
/>
0:000> I was preparing a sample memory leak application for an Advanced C# class at Microsoft this past week and debugging through it with SOS.DLL ("Son of Strike"). I did this by having the page hook up an event handler to a global event and then never remove the handler.
Mark's Blog of Random Thoughts
- Friday, September 1, 2006
SOS: finding the method bound to an EventHandler with WinDbg.
My prepared application was an ASP.NET application that would leak memory by holding references to the page objects after they had completed their work. then loaded this dump up into WinDBG and started poking around.
First, in VS.NET, so you need to familiarize yourself with WinDBG to do this.
/>
0:000> I was preparing a sample memory leak application for an Advanced C# class at Microsoft this past week and debugging through it with SOS.DLL ("Son of Strike"). I did this by having the page hook up an event handler to a global event and then never remove the handler.
Mark's Blog of Random Thoughts
- Friday, September 1, 2006
|
-
|
The Best from DevelopMentor
|
MORE
|
-
SOS: finding the method bound to an EventHandler with WinDbg.
My prepared application was an ASP.NET application that would leak memory by holding references to the page objects after they had completed their work. then loaded this dump up into WinDBG and started poking around.
First, in VS.NET, so you need to familiarize yourself with WinDBG to do this.
/>
0:000> I was preparing a sample memory leak application for an Advanced C# class at Microsoft this past week and debugging through it with SOS.DLL ("Son of Strike"). I did this by having the page hook up an event handler to a global event and then never remove the handler.
-
SOS: finding the method bound to an EventHandler with WinDbg.
My prepared application was an ASP.NET application that would leak memory by holding references to the page objects after they had completed their work. then loaded this dump up into WinDBG and started poking around.
First, VS.NET, so you need to familiarize yourself with WinDBG to do this.
/>
0:000> I was preparing a sample memory leak application for an Advanced C# class at Microsoft this past week and debugging through it with SOS.DLL ("Son of Strike"). I did this by having the page hook up an event handler to a global event and then never remove the handler.
|
|
|
