Lock(This)

[jpk420]

Hello All , I was readinf the lock concept and find that there is problem with lock(this) or lock(public type). what is the problem doing like that ? Please explain me with an example

[Ennis Ray Lynch Jr]

A good starting point for research is the documentation[^]. I think you would be surprised at the information available in MSDN.

Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. A man said to the universe: "Sir I exist!" "However," replied the universe, "The fact has not created in me A sense of obligation." --Stephen Crane

[Luc Pattyn]

Nah. MSDN documentation is like holiday brochures without pictures, nothing interesting there. :laugh:

Luc Pattyn [Forum Guidelines] [My Articles]

---

The quality and detail of your question reflects on the effectiveness of the help you are likely to get. Show formatted code inside PRE tags, and give clear symptoms when describing a problem.

---

[Ennis Ray Lynch Jr]

Actually, the particular article I referenced while sparse does indicate the common problems and a common solution in the remarks section. Although, most MSDN is total crap.

Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. A man said to the universe: "Sir I exist!" "However," replied the universe, "The fact has not created in me A sense of obligation." --Stephen Crane

[jpk420]

I check the documentation . I did not get that what was the problem . any way we are making lock on that object . So what matters if that is private or public? Please help me out

[Luc Pattyn]

you could as well ask why private and protected members exist at all. Why not make everything public? it is a matter of encapsulation, separation of concern, improving reliability, etc. :)

Luc Pattyn [Forum Guidelines] [My Articles]

---

The quality and detail of your question reflects on the effectiveness of the help you are likely to get. Show formatted code inside PRE tags, and give clear symptoms when describing a problem.

---

[jpk420]

No That i not mean at all . what i got confused is anyhow i am locking that object . So untill i done with my work no body can tamper it with . So even if i declare private or public i am holding a lock on that . So how that acces specifier will affect that . Sorry to trouble u .. bUt a good example will clear my doubt .. my brain is not able to leav this doubt unanswered.

[Luc Pattyn]

when your locker object is public I can lock it without your code being aware of it; so all your code would break right away. Don't make public what doesn't have to be public, that is one of the OO principles. :)

Luc Pattyn [Forum Guidelines] [My Articles]

---

The quality and detail of your question reflects on the effectiveness of the help you are likely to get. Show formatted code inside PRE tags, and give clear symptoms when describing a problem.

---

[PIEBALDconsult]

Yet with Reflection I can see your privates. :cool:

[Luc Pattyn]

You'd better think twice before applying reflection on me... :-\

Luc Pattyn [Forum Guidelines] [My Articles]

---

The quality and detail of your question reflects on the effectiveness of the help you are likely to get. Show formatted code inside PRE tags, and give clear symptoms when describing a problem.

---

[Leonardo Muzzi]

The problem with Lock(this) and Lock(type) is that these objects are public, so an external code could lock on them. So if your class is named YourClass, I can make a code like this:

YourClass obj = new YourClass();
lock(obj){ ... }

And that would probably deadlock your internal code. Same problem for a public type. Since it is commom to lock an object that you want to protect, it's not too dificult for a code like this to happen. The best approach is to create an object just for locking on it, instead of locking the class object. Make this locking object "static" and you get the same effect of locking a type.

Regards, Leonardo Muzzi