Creating an Interface in a class library c#

Question

0.00/5 (No votes)

See more:

I want to create a library project which acts as a sort of wrapper/intermediary class and has all my variables/functions to be used in other classes. Is there any efficiency in creating an interface within this library to store variables or that can easily just be declared in the library class itself?

Posted 8-Oct-15 21:48pm

Member 11971544

Updated 8-Oct-15 21:55pm

Manas_Kumar

v2

Add a Solution

Comments

Philippe Mori 9-Oct-15 12:53pm

You probably don't want to do that. This is not good design. Better to learn software development first...

2 solutions

Solution 1

Quote:
I want to create a library project which acts as a sort of wrapper/intermediary class and has all my variables/functions to be used in other classes

Why? Have you a specific requirement (e.g. you need a proxy) or do you see a general advantage in doing that?

Quote:
Is there any efficiency in creating an interface within this library to store variables or that can easily just be declared in the library class itself?

You know, there is no performance gain in using iterfaces. Interface has a very specific role in Object Oriented Programming, if you have any doubt then I suggest you studying a good OOP book (or, at least, read goodtutorials on the web).

Posted 8-Oct-15 21:59pm

CPallini

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)

F-ES Sitecore · Accepted Answer · 2015-10-08T22:19:00

Interfaces can't store anything, you'll still need the properties to be stored in a concrete class. Interfaces are only of use if you can see you needing different concrete implementations of the class that stores your properties. As we're talking data here, that's very unlikely, you normally use interfaces so you can have different implementations of code, however properties are properties. So I wouldn't bother with an interface.