You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
-
In your last sentence, do you mean to make one project where all interfaces can be placed? For example a project named 'Interfaces' with some logical structure in it based on the domain model. And all other projects with implementations would reference the Interfaces project? If this is fine, then I have another question; Is it a good practice to split up the Interfaces project into sub domains?Ozkan– Ozkan2018-07-26 08:34:31 +00:00Commented Jul 26, 2018 at 8:34
-
1Yeah, that's a pretty common pattern. If you have "MyProject.Core.dll" and "MyProject.ModuleA.dll", you might want to have a "MyProject.Interfaces.dll". That way you can have interfaces that are used by both libraries without creating circular depedencies.Avner Shahar-Kashtan– Avner Shahar-Kashtan2018-07-26 08:36:25 +00:00Commented Jul 26, 2018 at 8:36
-
Is it a good practice to split up the Interfaces project into sub domains then? So how will my solution look like in the solution explorer (in case of .NET). several implementation projects and several interface projects. what are the best practices for naming those projects. Any articles you recommend? I love reading about this.Ozkan– Ozkan2018-07-26 08:39:23 +00:00Commented Jul 26, 2018 at 8:39
-
Does this 'common pattern' have a name? Where can I read more about this?Ozkan– Ozkan2018-07-26 08:44:44 +00:00Commented Jul 26, 2018 at 8:44
-
I think you should ask a new question. Or come to C# Chat.Avner Shahar-Kashtan– Avner Shahar-Kashtan2018-07-26 10:20:36 +00:00Commented Jul 26, 2018 at 10:20
Add a comment
|
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you