|
|
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.
|
4 Articles match "2000","Sample"
|
The Latest from DevelopMentor
|
MORE
|
|
Using Rx (Linq to Events) with WPF
CLR uses 2.0.0.0. Next, I took a couple of the samples from the blog and ported
them them to WPF - specifically, I took the events sample listed here http://themechanicalbride.blogspot.com/2009/07/developing-with-rx-part-1-extension.html A recent series of blog entries at http://themechanicalbride.blogspot.com/ introduced
the the Rx framework (System.Reactive.dll) which is an assembly used in the Silverlight
toolkit
Mark's Blog of Random Thoughts
- Monday, August 3, 2009
SOS: finding the method bound to an EventHandler with WinDbg.
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"). said, this was a sample.
So, section 0 - VA=2000, VASize=504, FileAddr=200, FileSize=600
section 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. I did this by having the page hook up an event handler to a global event and then never remove the handler.
This,
Mark's Blog of Random Thoughts
- Friday, September 1, 2006
SOS: finding the method bound to an EventHandler with WinDbg.
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"). said, this was a sample.
So, section 0 - VA=2000, VASize=504, FileAddr=200, FileSize=600
section 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. I did this by having the page hook up an event handler to a global event and then never remove the handler.
This,
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.
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"). said, this was a sample.
So, section 0 - VA=2000, VASize=504, FileAddr=200, FileSize=600
section 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. I did this by having the page hook up an event handler to a global event and then never remove the handler.
This,
-
Using Rx (Linq to Events) with WPF
CLR uses 2.0.0.0. Next, I took a couple of the samples from the blog and ported
them them to WPF - specifically, I took the events sample listed here http://themechanicalbride.blogspot.com/2009/07/developing-with-rx-part-1-extension.html A recent series of blog entries at http://themechanicalbride.blogspot.com/ introduced
the the Rx framework (System.Reactive.dll) which is an assembly used in the Silverlight
toolkit
-
Wrapping the TAPI 3.0 API with C++/CLI
NET available on our samples page -- http://www.julmar.com/samples/tapi3wrapper.zip
Recently, With Windows 2000, Microsoft released a COM version of TAPI - dubbed TAPI 3.0 stream - basically the code that was in every TAPI sample provided by MS. New announcement - TAPI3 wrapper for .NET Recently, I released the ATAPI.NET project into the wild for people to be able to
easily
-
SOS: finding the method bound to an EventHandler with WinDbg.
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"). said, this was a sample.
So, section 0 - VA=2000, VASize=504, FileAddr=200, FileSize=600
section 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. I did this by having the page hook up an event handler to a global event and then never remove the handler.
This,
|
|
|
