i have a winform app in c# 2.0 .
i am reading an object's property in the main thread and changing it on a background thread.
i am using backgroundworker class.
should i lock the object before writing and reading
can anyone give me some code samples
multithreading in c# 2.0 and locking an object
Hot Topic
- ADO/SQLExpress Connection String Question
- Stepping through a unit test generates MDA FatalExecutionEngineError
- system.objectdisposedexception
- Exception while running load test on Trace Listener
- JIT Compilation optimizations
- Required Permission Caanot be Acquired Error
- Error when opening component containing OleDbDataAdapter
- Delay
- Failed to access IIS metabase, VS2005 RC
- about RasHangUp
.NET Development
- IEEE1394B programming
- How to Communicate Between Pocket PC and PC using VB.NET?
- easy winsock question
- User Authentication ASP/SQL
- webservice response prompts me to download .smi file
- SQL Server 2005 XML type looses spaces
- How do I check if object locked?
- Ado Vs Ado.net
- BUG? ldtoken with generic methoddef throws an MissingMethodException exception
- how can a web appliaction wil be treated on localhost
multithreading in c# 2.0 and locking an object
onethird13
Yes, you should lock the object if you want threadsafety.
If you won't introduce locks then you cannot rely upon object value as it can be changed by the other thread.
in the main and background threads you can wrap the code, where you access object properties with lock statments
lock(myObj)
{
//access myObj props here
}