How to use Dot Net Appropriately?

Well this post is intended to starters only like me, even I am a newbie programmer, but I learned/learning lot of new things in how to use .net appropriately, firstly, we need a few things in clarification:

1. Dot Net is only a library, like how we write our own classes, Microsoft Dot Net Team has written many strongly typed and well designed and managed code libraries.
2. Instead of each developer creating a code library for his own very task, in which way every developer maintains his/her code library, Microsoft created and maintained a General/yet specific code library which covers mostly all sort of functions. Example:I have a library for string comparer, but every developer used to have the same, Microsoft gave this functionality  in Dot Net library and made it common for all with well typed name.
3. All soft of Microsoft developed technologies can take use of this, as the library supports VB, C#, F#, C++ and even scripting can take advantage of this like POWERSHELL.
4. Developer need not include old Dot Net in his installer as basic versions/old versions come preinstalled in windows systems.

When it come to using .NET appropriately, it means, first search if the functionality we need is there/existing in .Net library; for example:

We want to create a code for making sure the object is backed before editing, then saved or discarded based on user wish to save changes, instead of using our own desired names for Method/Functions, >NET gives this features with its own managed library names, and for reference, this functionality is supported by IEditableObjectInterface under System.Components Namespace, more information can be found at MSDN.

Making use of Inheritance and Implements are the greatest methods to follow for any .NET programmer.

All the code libraries in .NET are based on this methods only, like WPF implements INotifyPropertyChanged, and many classes are inherited from base classes.

First thing to do is try to give a read of what Interfaces are given in .NET, mostly the ComponentModel Namespace should do for generic purposes.

HAPPY NEW YEAR 2013