You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, object values are simply strings generated by [DebuggerDisplay] and/or .ToString(); We need to be able to take a snapshot of the object's state if we ever want to be able to move closer to debugger-like functionality.
We could:
Create a deep copy of the object (hard, slow, complete)
Track external property changes differently, associating it with the object (easy, faster, far from complete)
This would probably be an optional feature, given potential performance implications.
The text was updated successfully, but these errors were encountered:
Given the new AppDomain separation, this has gotten a bit trickier. The snapshot will need to be taken in the AppDomain, and represented in a way that can be sent back to the host domain.
Currently, object values are simply strings generated by [DebuggerDisplay] and/or .ToString(); We need to be able to take a snapshot of the object's state if we ever want to be able to move closer to debugger-like functionality.
We could:
This would probably be an optional feature, given potential performance implications.
The text was updated successfully, but these errors were encountered: