Hi Kevin, thanks for explaining this, i have one more question, Does GetOrders exist else where? in another class which has the implementation?

Shawn

After reading your webpage : http://www.kevin_s_goff.typepad.com/
10/05 tip: Interfaces (Part 1 of 3)

Noting this excerpt :A common definition/description of an interface is a contract that guarantees how a class will behave, and what properties and methods the class will contain. When you create an instance of a class that implements the interface, you can be assured that the class will contain every PEM that the interface defined. Think of the interface as the bullet point list of what will be in the class.

I see what an interface can do.

Essentially, it can expose the methods of a class, that may not be part of the assembply that we are in, right?

Shawn

>just as an example...
>
>

>
>	public interface IOrderObject
>	{
>		string GetOrders(int nCustomerId);	
>          }
>

>
>The client side can code against this interface, even though the actual code for GetOrders resides on another server.
>
>

>MyInterfaces.IOrderobject oRemoteOrderObject;
>
>oRemoteOrderObject = (IOrderObject)oMyRemotingClass.GetRemoteObject();
>string cMyResults = oRemoteOrderObject.GetOrders(nCustomerID);
>
>// oRemoteOrderObject is strongly typed...you'll be able to see the available props and methods in intellisense
>

>
>
>
>
>
>Kevin