What should be created first interface or class in asp.net?

Question

1.00/5 (2 votes)

See more:

We use interfaces in our application but what is the correct way to add them in our application?
Shall we create an interface first and declare all the functions needed in a class Or Shall we define all our functions inside the class and then declare them in the interface?Whats the correct way?

Posted 5-Dec-13 6:34am

Sumit Bhargav

Add a Solution

Comments

phil.o 5-Dec-13 13:24pm

And what difference do you think it makes? Normally sanity would be to define the interface and then implement it in a concrete class, but nothing prevents you from doing the contrary; as long as interfaces and their implementation are here at compile time.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Ron Beyer · Answer 1 · 2013-12-05T07:40:00

There is no right way to do this. Its a Chicken and Egg problem, either you start with the chicken (class) or the egg (interface).

Personally I start with the interface then write one concrete class and adjust the interface as needed. Then once I get the functionality down, I can write the other concrete classes.

Just keep in mind, don't create interfaces for the sake of creating interfaces. Only create interfaces when you need to define a contract for other concrete classes to implement.

You can also create interfaces (at least in VS Standard or above, not sure about express) by right clicking on a class and selecting Refactor>Extract Interface.