3 implementations of IObjectReference
System.Private.CoreLib (2)
src\libraries\System.Private.CoreLib\src\System\Reflection\ParameterInfo.cs (1)
13, IObjectReference
src\libraries\System.Private.CoreLib\src\System\UnitySerializationHolder.cs (1)
15public sealed class UnitySerializationHolder : ISerializable, IObjectReference
System.Windows.Forms.Tests (1)
System\Windows\Forms\BinaryFormat\WinFormsBinaryFormattedObjectTests.cs (1)
86private struct ReplicatedJsonData : IObjectReference
25 references to IObjectReference
mscorlib (1)
src\libraries\shims\mscorlib\ref\mscorlib.cs (1)
752[assembly: System.Runtime.CompilerServices.TypeForwardedTo(typeof(System.Runtime.Serialization.IObjectReference))]
netstandard (1)
netstandard.cs (1)
1774[assembly: System.Runtime.CompilerServices.TypeForwardedTo(typeof(System.Runtime.Serialization.IObjectReference))]
System.Private.DataContractSerialization (3)
System\Runtime\Serialization\Globals.cs (1)
113s_typeOfIObjectReference ??= typeof(IObjectReference);
System\Runtime\Serialization\ReflectionReader.cs (1)
54if (obj is IObjectReference objectReference)
System\Runtime\Serialization\XmlObjectSerializerReadContext.cs (1)
406public object GetRealObject(IObjectReference obj, string id)
System.Private.Windows.Core (8)
System\Private\Windows\BinaryFormat\Deserializer\ClassRecordDeserializer.cs (1)
26_onlyAllowPrimitives = @object is IObjectReference;
System\Private\Windows\BinaryFormat\Deserializer\Deserializer.cs (5)
17/// This has some constraints over the BinaryFormatter. Notably it does not support all <see cref="IObjectReference"/> 39/// <see cref="IObjectReference"/> makes deserializing difficult as you don't know the final type until you've finished 44/// <see cref="IObjectReference"/> is really the only practical way to represent singletons. A common pattern is to 45/// nest an <see cref="IObjectReference"/> object in an <see cref="ISerializable"/> object. Specifying the nested 347if (@object is IObjectReference objectReference)
System\Private\Windows\BinaryFormat\Deserializer\IDeserializer.cs (1)
27/// Objects are considered incomplete if they contain references to value or <see cref="IObjectReference"/> types
System\Private\Windows\BinaryFormat\Deserializer\ObjectRecordDeserializer.cs (1)
92&& (value is IObjectReference
System.Resources.Extensions (8)
System\Resources\Extensions\BinaryFormat\Deserializer\ClassRecordDeserializer.cs (1)
27_onlyAllowPrimitives = @object is IObjectReference;
System\Resources\Extensions\BinaryFormat\Deserializer\Deserializer.cs (5)
20/// This has some constraints over the BinaryFormatter. Notably it does not support all <see cref="IObjectReference"/> 42/// <see cref="IObjectReference"/> makes deserializing difficult as you don't know the final type until you've finished 47/// <see cref="IObjectReference"/> is really the only practical way to represent singletons. A common pattern is to 48/// nest an <see cref="IObjectReference"/> object in an <see cref="ISerializable"/> object. Specifying the nested 352if (@object is IObjectReference objectReference)
System\Resources\Extensions\BinaryFormat\Deserializer\IDeserializer.cs (1)
28/// Objects are considered incomplete if they contain references to value or <see cref="IObjectReference"/> types
System\Resources\Extensions\BinaryFormat\Deserializer\ObjectRecordDeserializer.cs (1)
91&& (value is IObjectReference
System.Runtime (1)
artifacts\obj\System.Runtime\Debug\net10.0\System.Runtime.Forwards.cs (1)
700[assembly: System.Runtime.CompilerServices.TypeForwardedTo(typeof(System.Runtime.Serialization.IObjectReference))]
System.Runtime.Serialization.Formatters (3)
System\Runtime\Serialization\ObjectManager.cs (3)
244holder.SetObjectValue(((IObjectReference)(holder.ObjectValue)).GetRealObject(_context), this); 257} while ((holder.ObjectValue is IObjectReference) && (tempObject != holder.ObjectValue)); 1236if (_object is IObjectReference)