StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POClass implementations in interface dll?
primarykey
Id
1840026
data
AcceptedAnswerId
1840089
AnswerCount
4
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-12-03T14:01:49.053
FavoriteCount
0
LastActivityDate
2009-12-03T15:12:22.580
LastEditDate
LastEditorUserId
0
OwnerUserId
97118
ParentId
0
PostTypeId
1
Score
0
ViewCount
2616
LastEditorDisplayName
text
Body
my problem: Inside an application, all interfaces are declared inside an own dll(project "interfaces", for example). Inside project interfaces, there are many class implementations, too. Now I need one of this implemented classes inside another project and get a ring dependency because this project is also a reference in project interfaces. So, what is the best way to get around this ring dependency? Could it be possible that this is a big mistake in the design of the application? Schematic representation: IBigInterface.cs (everything in one file): <pre><code>interface ISomeInterfaceA { void SomeFunctionA(ClassB x); // ClassB from newProject.cs void SomeFunctionB(); } // // etc. // class ClassA { // // Code // } </code></pre> newProject.cs (everything in one file): <pre><code>class ClassB { // // used in interfaces.dll // } class ClassC { void SomeFunction(ClassA a) // ClassA from IBigInterface.cs { // // do something // } } </code></pre> First thing that comes into my mind would be sth. like: IBigInterface.cs: <pre><code>interface ISomeInterfaceA { void SomeFunctionA(IInterfaceB x); // use interface instead of a class void SomeFunctionB(); } interface IInterfaceB { // // declarations // } class ClassA { // // implementation // } </code></pre> newProject.cs: <pre><code>class ClassB : IInterfaceB // implementation of IInterfaceB { } class ClassC { void SomeFunction(ClassA a) { // // implementation // } } </code></pre> so that project newProject wouldn't be a reference in project interfaces anymore (although this means changes in the whole application). P.S.: I inherited this application so the idea of implementing classes in an interface-project was not my idea :). In General, I would create one file per class (so don't point to this :).
Tags
<c#><architecture><interface><class-design>
Title
Class implementations in interface dll?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USInno
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.