Contract(s) and Interface(s)?
Contracts or interfaces, agreements, boundaries and/or crossing points are crucial programming essentials. They enable component compliance through standard contracts, implementing interfaces nuts-and-bolts programming utilities.
Interfaces define contracts between types, ensuring a class implements specific members. If constraints are used to require types to initialize and use certain interface, any methods used in and for that interface can be called.
Contracts, standards, agreements, form part of the Fundamentals Toolkit for .NET Framework development and environments. Complying with standard contracts is part of the basics. Interfaces are also known as contracts. It defines a common set of members that all classes, participants must provide that implement and use this interface. They are used to equality comparison for example. Use of contracts or interfaces can be used for identifying errors, creating interface(s) for add-ins, add-ons, plug-ins and other key processes.
Key Exam Points
- Gain experience in implementing common interfaces
- Practice scenarios and contract(s), with real-world classes, allowing arrays of objects to be sorted, type conversions, as well as disposals of same.
This article is based on the 2nd edition of the Microsoft .Net Framework Application Training Kit with the purpose to help 70-536 Exam takers to succeed. I constantly look for ways to improve the content. Please leave a comment about this article or drop me a message if you would like to see changes for this site.