Recommendations for deep copying C# object

[d000hg]

Well as I said in the OP it is a plan B.

If I used sheer number of projects, and sheer number of classes and interfaces it's probably the biggest and most complicated thing I have ever ever worked on.

What? I said how big is the object, not the project. i.e. does it boil down to a few key-value pairs or hundreds of kilobytes of data.

Why would I use a C++ term for a C hash object? The term here is POCO. Plain Old CLR Object - Wikipedia, the free encyclopedia

Because most OO programming concepts are common to most OO languages? POD is referenced from that very article btw.

[suityou01]

The problem is that my class wraps a user control. So all objects need to be serialisable.

Additional information: Type 'System.Windows.Forms.UserControl' in Assembly 'System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' is not marked as serializable.

And I think this sets me back to square one.

[DimPrawn]

Sounds like another Suity disaster in the making.

Good luck with that

[DimPrawn]

Oh and

c# - Why are System.Windows.Forms.Control not marked as serializable? - Stack Overflow

[suityou01]

Sounds like another Suity disaster in the making.

Good luck with that

So I implemented IClonable and wrote my own clone method. Disaster averted

[Gittins Gal]

JSON is a subset of YAML I think.

[Churchill]

So I implemented IClonable and wrote my own clone method. Disaster averted

And you've just proved why C# is tulipe!

[eek]

And you've just proved why C# is tulipe!

No, I think all he has done is shown that a poor workman blames his tools...

[Churchill]

No, I think all he has done is shown that a poor workman blames his tools...

C# is still tulipe. Whether or not Suity makes a balls of it or not ;-)

[d000hg]

And you've just proved why C# is tulipe!

Because it provides a handy interface to let you do this?

C# is pretty neat, generally speaking.