Skip to main content

Common .Net Interview Questions and Why are they asked?

There are many .Net Questions that every interviewer(in general) asks.
Through this, I am starting a series of discussions where in I'll be discussing these questions and provide ample satisfactory answers to them.

The intent here is to realise the importance of these questions and help the needy(those who are preparing for interviews) and also who believe in knowing the basics rather than just blindly implementing the .Net classes/Interfaces.

Starting the First part of this series is All time Classic question #1

Question: What is the difference between Abstract Classes and Interface?

The moment this question is asked the candidates generally start uttering the bookish definitions, some of them are .
a) Access modifiers: Interfaces--Implicitly Public() , Classes can use use Access Modifiers.
b) No implementation in Interfaces, Classes can have implementations as well.
c)Abstract classes can't be instantiated .

Some more experienced candidates might get into some further details, However the basic things to understand here is  if these two are that much close in implementing functionality why do we have these two separately in C#

I'm not trying to be an Expert here, all I am trying, is to get rid of this anxious question once for all by exploring it from some possible angles.

OOPS principle that is being tested by this question: Polymorphism

Without going into Polymorphism details, both of these(Interfaces and Abstract Classes) are a ways of achieving Polymorphism in the Code.

Let's consider an example

public void Gadgets(MyGadget gadget){

}

This method could accept any object that implemented MyGadget as the gadget argument, even though the implementations of MyGadget might be quite different.

 A Class may inherit from only one base class(in C# ), so if you want to use abstract classes to provide polymorphism to a group of classes, they must all inherit from that class.
Abstract classes may also provide members that have already been implemented. Therefore, you can ensure a certain amount of identical functionality with an abstract class, but cannot with an interface.

 Decide whether to use an interface or an abstract class to provide polymorphism for your components.

  • If creating multiple versions of your component is anticipated, create an abstract class. Abstract classes provide a simple and easy way to version components. By updating the base class, all inheriting classes are automatically updated with the change. Interfaces, on the other hand, cannot be changed once created. If a new version of an interface is required,  a whole new interface must be created.

  • If the functionality youbeing created will be useful across a wide range of disparate objects, use an interface. Abstract classes should be used primarily for objects that are closely related, whereas interfaces are best suited for providing common functionality to unrelated classes.

  • If designing small, concise bits of functionality, use interfaces. If  designing large functional units, use an abstract class.

  • If  common, implemented functionality among all implementations of the component is intended, use an abstract class. Abstract classes allow to partially implement class, whereas interfaces contain no implementation for any members.


Hope this helps in making the decision as to when to use interfaces and when to use Abstract Classes,

Soon, I'll try to cover other commonly asked interview question.

Till next we connect, Happy Coding.

 
Labels:

Comments

Post a Comment

Popular posts from this blog

Authentication using Social Networking portals(Facebook, Gmail, and Yahoo)

There are tons of sites, which offer sign on using the social networking site credentials (Facebook, gtalk, twitter and the list continues).It can be termed a “SINGLE SIGNON” and offers a lot of benefits compared to traditional database authentication approach. However, not storing user credentials in the DB imposes an additional risk. How to track who all logged into the system. Now the question is, which approach to follow. The best approach is to use inbuilt asp.net users for storing the logging info about user activities and using single signon technique for authentication. This article will explore the approach and provide the details of implementation using some third party libraries and customizing it to the requirements. The Authentication will be done using the following networking portals Yahoo  Gmail Facebook    Special thanks to my friend Sumit Khandelwal, for implementation of Facebook part (in fact he did it all!!) Except Facebook, all other ca...
2 comments
Read more

WPF Overview-Part-II

This post is in continuation to the last post. In this Post I’ll be exploring the Dependency Properties Dependency properties are similar to CLR properties with more advanced and complex features. The main difference between the CLR properties and dependency properties is, that the value of a normal .NET property is read directly from a private member in your class, whereas the value of a DependencyProperty is resolved dynamically when calling the GetValue() method that is inherited from DependencyObject . In case this description did not make sense, no need to worry, It will become clear by the time you reach end of this article. How the Value is Resolved in Dependency properties Every time a dependency property is accessed, it internally resolves the value by following the precedence from high to low. It checks if a local value is available, if not, check if a custom style trigger is active and I the similar manner continues until it finds a value. At last the default value is alwa...
Post a Comment
Read more

Asp.Net 4.0: An Overview-Part-III

This is the last post in the series which will explore the following new features of ASP.Net 4.0  Performance Monitoring for Individual Applications in a Single Worker Process Web.config File Refactoring Permanently Redirecting a Page Expanding the Range of Allowable URLs Performance Monitoring for Individual Applications in a Single Worker Process It is a common practice to host multiple ASP.NET applications in a single worker process, In order to increase the number of Web sites that can be hosted on a single server. This practice results in difficulties for server administrators to identify an individual application that is experiencing problems. ASP.NET 4 introduces new resource-monitoring functionality introduced by the CLR. To enable this functionality, following XML configuration snippet is added to the aspnet.config configuration file.(This file is located in the directory where the .NET Framework is installed ) <?xml version="1.0" encoding="UTF-8...
Post a Comment
Read more