When should you use Abstract Class vs Interface while
programming? Give 1 Example
Answer Posted / pravin shrirao
Interfaces are used when we want classes should follow the
rules strictly. Rules like naming coventions e.g. if in
customer class one developer add method AddCustomer other
developer while implementing Invoice class could write
method name InvoiceAdd and also could change the Signiture
rules. for addition of customer we have at client code as
Cutomer.AddCustomer(A,B,C); and Invoice.InvoiceAdd(A,B)
To maintain uniformality if we declare interface and define
method Add(A,B) in that interface and implement that
interface in both the classes then the code will be uniform
all over the classes where ever we have implemented
interface and also all concrete classes must contain
methods which are defined in the interfaces.
| Is This Answer Correct ? | 22 Yes | 5 No |
Post New Answer View All Answers
hi, kindly send WWF(.net 3.5) pdf notes to my id. thanx in advance, chays
Explain write back and write through caches? : Dot net architecture
Explain the difference between primary & secondary storage device? : .NET Architecture
How to implement the display in the class printdoc (how to resolve the naming conflict) a: no naming conflicts
What is an interrupt? : Dot net architecture
Explain how cache is used? : Dot net architecture
Explain about generation?
8. Oop-Why and were we use Interfacse and Abstract class.
Explain about common language infrastructure?
What does this do? Gacutil /l | find /i "corillian"
What is an interrupt? : .NET Architecture
What is .net mobile utility controls. Explain with an example? : Microsoft dot net mobile
What is the purpose of cache? : Dot net architecture
any one can explain about projectarchitecture and project approach briefly
HttpHendler and HttpModules