Comments on: Guaranteeing Disposal Of UserControls In ASP.NET http://davybrion.com/blog/2009/04/guaranteeing-disposal-of-usercontrols-in-aspnet/ inquisitive: adjective. given to inquiry, research, or asking questions; eager for knowledge; intellectually curious Sun, 20 May 2012 21:55:00 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Davy Brionhttp://davybrion.com/blog/2009/04/guaranteeing-disposal-of-usercontrols-in-aspnet/comment-page-1/#comment-33168 Davy Brion Mon, 22 Mar 2010 12:03:26 +0000 http://davybrion.com/blog/?p=1280#comment-33168 @Dinothat would work as well, though you're required to add each instance you want to see disposed to the HttpContext.Current.Items dictionary with a unique key to prevent overwriting other instancesin a way it would indeed be simpler, yet it's also more error prone i think @Dino

that would work as well, though you’re required to add each instance you want to see disposed to the HttpContext.Current.Items dictionary with a unique key to prevent overwriting other instances

in a way it would indeed be simpler, yet it’s also more error prone i think

]]> By: Dino Chiesahttp://davybrion.com/blog/2009/04/guaranteeing-disposal-of-usercontrols-in-aspnet/comment-page-1/#comment-33152 Dino Chiesa Mon, 22 Mar 2010 11:31:57 +0000 http://davybrion.com/blog/?p=1280#comment-33152 Davy, you sure you need all that? why not just register an Application_EndRequest() method in global.asax.cs, iterate through the HttpContext.Current.Items dictionary, and call Dispose as necessary (if the object is IDisposable). If you make the assumption that anything IDisposable needs to be Disposed when the request context goes out of scope, then the solution is much simpler than what you provided. You could also constrain the situation byb assuming "anything stored in request context that's a DataContext should be Disposed."Also, see this post from a while back from Keith Craig. http://blogs.vertigo.com/personal/keithc/Blog/archive/2007/06/28/linq-to-sql-and-the-quote-request-scoped-datacontext-quote-pattern.aspx Davy, you sure you need all that? why not just register an Application_EndRequest() method in global.asax.cs, iterate through the HttpContext.Current.Items dictionary, and call Dispose as necessary (if the object is IDisposable). If you make the assumption that anything IDisposable needs to be Disposed when the request context goes out of scope, then the solution is much simpler than what you provided.
You could also constrain the situation byb assuming “anything stored in request context that’s a DataContext should be Disposed.”

Also, see this post from a while back from Keith Craig.
http://blogs.vertigo.com/personal/keithc/Blog/archive/2007/06/28/linq-to-sql-and-the-quote-request-scoped-datacontext-quote-pattern.aspx

]]> By: Getting Your ASP.NET UserControl Disposed … At All Times | Kristof Rennen's Bloghttp://davybrion.com/blog/2009/04/guaranteeing-disposal-of-usercontrols-in-aspnet/comment-page-1/#comment-11833 Getting Your ASP.NET UserControl Disposed … At All Times | Kristof Rennen's Blog Thu, 09 Apr 2009 17:15:18 +0000 http://davybrion.com/blog/?p=1280#comment-11833 [...] Davy explains how he solved our problems in his blog post about the topic: Guaranteeing Disposal Of UserControls In ASP.NET [...] [...] Davy explains how he solved our problems in his blog post about the topic: Guaranteeing Disposal Of UserControls In ASP.NET [...]

]]>