Hi All,
Kindly let me know about object disposal in multithreaded program. I am particularly interested in knowing object disposal whenever thread is aborted.
Any help (Explination, Articles and others) is very much appreciated.
With Regards,
kalai
Object disposal while thread is aborting
Hot Topic
- Invoke without dedicated Delegate
- How to use ActiveX Control Importer (Aximp.exe)
- HTML Mail using SmtpClient
- Datareader to object relationship/mapping.
- DateTime "data type mismatch" in C# and Access
- problem to connect at imap server
- Soz, once again confused about tcp, sync and asynch!
- IE Hosted Form not working on Windows Server 2003 w/ SSL
- JOIN Select Against an XML/Re-query Dataset with JOIN
- Remote proxy has no channel sink
.NET Development
- problem with CueStream in WMS
- how to open ur custom file format in ur application
- XmlSerializer or custom serialization?
- Data Access with Access Database
- How to Hide original IP while using HttpWebRequest/Proxy support
- Intellisence Support for Custom Config Sections
- Application queries in a xml file
- permissions
- Web.Config or Machine.Config - which preceeds?
- SQL to retrievedata
Object disposal while thread is aborting
rccopter
Hi Lucian,
Thank you so much.
I have avoided calling Thread.Abort() method. Sure Reliability is restored.
Thanks & Regards,
kalai
Pape
Do a Google search for: chris brumme reliability. Search in msdn for "Reliability Best Practices". Of course the most important issue is architectural. Do you really have to Abort threads This is a dangerous practice. .NET 2.0 makes code more reliable (critical finalizer, SafeHandle, constrained regions; http://msdn.microsoft.com/msdnmag/issues/05/10/Reliability/), but this doesn't mean that you should do it just because you can :).
Dispose, Finalization, and Resource Management:
http://www.bluebytesoftware.com/blog/PermaLink.aspx guid=88e62cdf-5919-4ac7-bc33-20c06ae539ae