Where should the Interfaces class be placed in the .NET class library?

Question

I am curious about the developer's opinion / practice about where class classes should ideally be placed in the .NET class library. Should they be contained in their own dedicated library as part of the solution, such as MyCompany.AccountPackage.Interfaces?

If they have their own namespace, for example. MyCompany.AccountPackage.MasterAccounts.Interfaces?

Any other thoughts / opinions appreciated?

Is there a good guide demonstrating how to structure the .Net library (or even better, a solution), demonstrating in general which classes / interfaces should normally be displayed in the standard library.

Thanks D.

Answer 1

Short answer:

, .

, BCL - IEnumerable<T> System.Collections.Generic, .

---

:

.

(a-la MEF) ?

, , , , .

, IoC?

, , .

Answer 2

, , , .

, - , , . , , . , - (, ).

, , .NET System.Collections.Generic, ; , . , . , .

, , , . , , Microsoft Access, , Sql. .

, , . , , , , - , .

Answer 3

: .

99% , . , . , .

/ , . :

• ,
• ( )
• "" (.. , )

" " :

• " "
• " " ( , , )

, ( 1% ).

, , , :

• ( , , ).

" " , . , , .

? , . , .

:

- . , , :

• MyCompany.AccountPackage.MasterAccounts
• , MyCompany.AccountPackage.MasterAccounts
• - MyCompany.AccountPackage.MasterAccounts.SQLMasterAccounts MyCompany.AccountPackage.MasterAccounts.Implementation.

?

, using MyCompany.AccountPackage.MasterAccounts.Interfaces.

, intellisense ( ), , .

Answer 4

:

.NET DLL

:

• ?

• . ?

• , dll?

• Have you thought about scalability and service?