|
|
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
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 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 provides experienced.NET developers with practical knowledge and techniques for building robust, scalable, and highly available.NET applications.
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 class libraries and the C# language are evolving in.NET 3.5 Use C# 3.0 and C# 4.0? and Dublin.
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. Note: it appears that GCRoot doesn't work well inside VS.NET 2005 - apparently the SOS debugging extension is using some debugger API which isn't fully supported in VS.NET, so you need to familiarize yourself with WinDBG to do this. />. love SOS and WinDBG. But as I said, this was a sample. Next, I used ADPLUS.VBS to take a hang dump of the process.
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. Note: it appears that GCRoot doesn't work well inside VS.NET 2005 - apparently the SOS debugging extension is using some debugger API which isn't fully supported in VS.NET, so you need to familiarize yourself with WinDBG to do this. />. love SOS and WinDBG. But as I said, this was a sample. Next, I used ADPLUS.VBS to take a hang dump of the process.
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. Note: it appears that GCRoot doesn't work well inside VS.NET 2005 - apparently the SOS debugging extension is using some debugger API which isn't fully supported in VS.NET, so you need to familiarize yourself with WinDBG to do this. />. love SOS and WinDBG. But as I said, this was a sample. Next, I used ADPLUS.VBS to take a hang dump of the process.
-
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. Note: it appears that GCRoot doesn't work well inside VS.NET 2005 - apparently the SOS debugging extension is using some debugger API which isn't fully supported in VS.NET, so you need to familiarize yourself with WinDBG to do this. />. love SOS and WinDBG. But as I said, this was a sample. Next, I used ADPLUS.VBS to take a hang dump of the process.
|
|
|