can we inherit more then on class in asp.net aspx page ?

Question

I want to inherit more then one class is there any method ?

For instance in login.aspx page:

<%@ page  language="c#" codefile="nishant.aspx.cs" autowireup="true" inherit="nishant"%>

now code behind file

nishant.aspx.cs:

class nishant
{
//code...
}

class bill
{
//code.....
}

now i want to inherit bill class then how i will ?

Answer 1

.NET does not support multiple inheritance, this includes asp.net, so no, this is not possible.

You can have your nishant class inherit from the bill class or the other way around, if you want to share functionality. You page can then inherit from the inheriting class and access the functionality of both.

Another option is to inherit from one class and implement an interface (or several interfaces), but the fact that you can implement more than one interface is not the same as multiple inheritance.

There are other things that can be done, depending on what exactly you are trying to achieve (I am primarily thinking about composition versus inheritance).

Answer 2

No. By nature, .Net allows only single inheritance. At best you could implement an interface, but you will still have to have the code in your nishant class or extract the functionality into your bill class and make function calls.

Although in the case you mention, this is not actually multiple inheritance. Your nishant class must be of type System.Web.UI.Page. So if you create a library with a "bill class", you can then inherit it.

public class bill : System.Web.UI.Page
{
    // Your custom code
}

///

public class nishant : bill
{

}

Answer 3

.NET does not support multiple inheritance (one class that inherit from two or more classes).

However you can have as many parent class as you want. Have a look at the decorator pattern.

Or use interfaces, you can have more than one.

Answer 4

Multiple inheritance is not allowed. The only way is:

public class Bill : Page
{ }

public class Nishant : Bill
{ }

But rather you should think about your design. Such approach is usually not needed.