C# or .Net features to cut off assuming no backward compatibility needed?
Posted
by
Gulshan
on Programmers
See other posts from Programmers
or by Gulshan
Published on 2011-01-26T15:01:52Z
Indexed on
2011/02/05
15:33 UTC
Read the original article
Hit count: 333
Any product or framework evolves. Mainly it's done to catch up the needs of it's users, leverage new computing powers and simply make it better. Sometimes the primary design goal also changes with the product. C# or .net framework is no exception. As we see, the present day 4th version is very much different comparing with the first one. But thing comes as a barricade to this evolution- backward compatibility.
In most of frameworks/products there are features would have been cut off if there was no need to support backward compatibility. According to you, what are these features in C#/.net?
Please mention one feature per answer.
© Programmers or respective owner