c# - !(ReferenceEquals()) vs != in Entity Framework 4 -
As long as no one overrides a particular behavior defined for the object, ... compare the references.
Sets in property, I have usually used patterns
private MyType myProperty; Public MyType MyProperty {set {if (myProperty! = Value) {myProperty = value; // NotifyPropertyChanged}}}
However, if the if
statement is replaced in the code generated by the entity framework
(reference references (myProperty, value))
The use of referenceEquals is more clear (as I think all C # programmers do not know that == does the same thing Is not override if it is). / P>
Do I have to save between two different types? Are they probably accounting for the possibility that Poko designers have ==
? Can override? In essence, if I have not overridden, then ==
contextExcus ()
instead! Cementix:
-
ReferenceEclocks ()
should be used if you think the objects are the same (check the identity). -
Object. If you think the objects have the same value (parity check)
== ()
used only for the fixed type can go . Then use it for equality.
Of course the opposite counterparts are calculated accordingly.
सीएसएचआरपी उदाहरण...
ReplyDeleteक्लिपबोर्ड के नमूनों की नकल करना