Interface-based programming

From: Patrick Kristiansen (patrick_at_sixulon.dk)
Date: 09/25/04 

Date: 25 Sep 2004 09:01:27 -0700

Hi group!

I've been reading Juval Löwys "Programming .NET Components", and I
think it is a very good book, giving nice guidelines on how to really
exhaust the possibilities of .NET in general.

Juval Löwy is indeed an advocate of using interface-based programming
(he wrote a chapter dedicated to it, and he's using it througout the
book).

I have one simple question. When designing your own components, is it
true - according to the rules of interface-based programming - that
you should create interfaces for your clients to use, and advertise
for them to do so? So every time I design a class, it should have a
corresponding interface?

Regards,
Patrick

Relevant Pages

  • Re: How to Get Compiler Version at Run Time?
    ... Disregard my last post. ... "Leo Violette" wrote in message ... Here are a couple links I quickly found which seem to discuss the issue (though I didn't read them in detail - I originally discovered this technique in the book "Programming .NET Components" by Juval Lowy - he's recognized by MSFT as a leading .NET expert): ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Best professional/advanced windows forms book (C#)
    ... Programming .NET components, second Edition by Juval Lowy. ... >>From the reviews of amazon.com I found these are the best books for ...
    (microsoft.public.dotnet.framework.windowsforms)