Explain current thinking around IClonable.

Question

Hi.. Ques : Hello friend please Explain current thinking around IClonable in ASP.NET.

Shen Hengbin · Answer

I hope this post can help you , from effective c# . http://www.diranieh.com/NETCSharp/EffectiveCS.htm#27._Avoid_ICloneable And also if you have used ICloneable in your base class which is not sealed , there is a bug with it. Because it is not type safe , the sub class's default Clone() would return parent class not itself.

Vulpes · Answer

Many developers feel that, as there's no generic version and few methods take an ICloneable parameter anyway, ICloneable is not worth implementing. As the Clone() method returns an object, you always have to cast it to its actual type before you can do anything with it. Another problem is that it's not clear from the name whether you're implementing a shallow or a deep clone. This doesn't of course mean that you shouldn't write clone methods for your classes - just that there's no compelling reason for them to have the same signature as the ICloneable.Clone() method.

Explain current thinking around IClonable.

Insert Link

Embed YouTube Video

Table Options

Insert Image

Answers (2)