Can a class that implments an Interface declare a member that differs from the Interface definition?
I thought the answer to this question was no
Is the above leagal or does the class have to declare members that exactly match the Interface definition?
public interface Iface
{
void func1(string name);
void func2(string name, string surname);
}
public class MyClass : IFace
{
public void func1(string name, int age);
public void func2(string name, string surname, string address);
}
Is the above leagal or does the class have to declare members that exactly match the Interface definition?
Hi,
Yes, because, the declared class have different parametered function. then it is considered that different function through function overloading.
But you must to implement the Interface function in the declared class MyClass.
Yes, because, the declared class have different parametered function. then it is considered that different function through function overloading.
But you must to implement the Interface function in the declared class MyClass.
No. It isn't complete
public interface Iface
{
void func1(string name);
void func2(string name, string surname);
}
public class MyClass : IFace
{
public void func1(string name); //MUST implement
public void func2(string name, string surname); //MUST implement
public void func1(string name, int age);
public void func2(string name, string surname, string address);
}
Ok, that is what I thought - but here is my problem.
I have inherited a project from another developer - based on NopCommerce.
The original source from NopCommerce contains two files
INopService.cs
NopService.cs
Extracts to follow
INopService
NopService
This code compiles fine - but the same two files in my source don't and generate the error that a member does not exist in the class implementing the interface.
My question then is how can the above compile with the Nop Commerce release?
I have inherited a project from another developer - based on NopCommerce.
The original source from NopCommerce contains two files
INopService.cs
NopService.cs
Extracts to follow
INopService
public interface INopService
{
...
void UpdateOrderBillingInfo(int orderId, string firstName, string lastName, string phone, string email, string fax, string company, string address1, string address2, string city, string region, string country, string postalCode, string usernameOrEmail, string userPassword);
void UpdateOrderShippingInfo(int orderId, string firstName, string lastName, string phone, string email, string fax, string company, string address1, string address2, string city, string region, string country, string postalCode, string usernameOrEmail, string userPassword);
...
}
NopService
public class NopService : INopService
{
...
public void UpdateOrderBillingInfo(int orderId, string firstName, string lastName, string phone, string email, string fax, string company, string address1, string address2,
string suburb, string city, string stateProvinceAbbreviation, string countryThreeLetterIsoCode, string postalCode, string usernameOrEmail, string userPassword)
public void UpdateOrderShippingInfo(int orderId, string firstName, string lastName, string phone, string email, string fax, string company, string address1, string address2,
string suburb, string city, string stateProvinceAbbreviation, string countryThreeLetterIsoCode, string postalCode, string usernameOrEmail, string userPassword)
}
This code compiles fine - but the same two files in my source don't and generate the error that a member does not exist in the class implementing the interface.
My question then is how can the above compile with the Nop Commerce release?
This is why I am posting here - did a forum post at NC but no responses.
I just checked and I posted the code from my version of the source instead of the original NP code. Here is the code from their files NCC denotes NopCommerce Class and NCI denotes the interface. I have also attached the original files.
As you can see they are still different.
I searched the source for all instances of UpdateOrder and only these were found.
Just confused as to why the downloaded source for NC 2.6 compiles?
INopService.cs
I just checked and I posted the code from my version of the source instead of the original NP code. Here is the code from their files NCC denotes NopCommerce Class and NCI denotes the interface. I have also attached the original files.
As you can see they are still different.
I searched the source for all instances of UpdateOrder and only these were found.
Just confused as to why the downloaded source for NC 2.6 compiles?
NCI void UpdateOrderBillingInfo(int orderId, string firstName, string lastName, string phone, string email, string fax, string company, string address1, string address2, string city, string region, string country, string postalCode, string usernameOrEmail, string userPassword);
NCC void UpdateOrderBillingInfo(int orderId, string firstName, string lastName, string phone, string email, string fax, string company, string address1, string address2, string city, string stateProvinceAbbreviation, string countryThreeLetterIsoCode, string postalCode, string usernameOrEmail, string userPassword)
NCI void UpdateOrderShippingInfo(int orderId, string firstName, string lastName, string phone, string email, string fax, string company, string address1, string address2, string city, string region, string country, string postalCode, string usernameOrEmail, string userPassword);
NCC void UpdateOrderShippingInfo(int orderId, string firstName, string lastName, string phone, string email, string fax, string company, string address1, string address2, string city, string stateProvinceAbbreviation, string countryThreeLetterIsoCode, string postalCode, string usernameOrEmail, string userPassword)
INopService.cs
The NC 2.6 code you just posted will compile because the function signatures match. Remember that the compiler doesn't care one bit about the names of parameters. All it cares about is the name of your method, the number of parameters, and the types of each parameter. This is how the compiler determines which version of an overload to use when it is compiling your code.
In your case, the NC 2.6 class correctly defines two methods which both correspond to a method definition in the interface with the appropriate name, number of parameters, and parameter types. It does not matter that the interface says "region" where the class says "stateProvinceAbbreviation
In your case, the NC 2.6 class correctly defines two methods which both correspond to a method definition in the interface with the appropriate name, number of parameters, and parameter types. It does not matter that the interface says "region" where the class says "stateProvinceAbbreviation