Versioning with the new and override Keywords
A large proportion of the software written today is, as mentioned earlier developed by using class libraries often written by other remote programmers. Just like most standalone software applications are upgraded to versions with more features and less bugs, class libraries undergo a similar evolving process. It is a fairly painless process to upgrade to the latest version of the Doom game, but what if you want to upgrade the .NET Framework class library on which your application is heavily dependent. What if the library developers for example didn't like the name WriteLine anymore and changed it to PrintLine in the latest upgrade? You would then have to painstakingly substitute all the WriteLine ...
Get C# Primer Plus now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
