Timeline for Where to put interface in .Net
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 26, 2018 at 10:20 | comment | added | Avner Shahar-Kashtan | I think you should ask a new question. Or come to C# Chat. | |
| Jul 26, 2018 at 8:44 | comment | added | Ozkan | Does this 'common pattern' have a name? Where can I read more about this? | |
| Jul 26, 2018 at 8:39 | comment | added | Ozkan | 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. | |
| Jul 26, 2018 at 8:36 | comment | added | Avner Shahar-Kashtan | Yeah, 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. | |
| Jul 26, 2018 at 8:34 | comment | added | Ozkan | 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? | |
| Jul 7, 2013 at 15:47 | vote | accept | jmoreno | ||
| Jul 6, 2013 at 19:24 | history | edited | Avner Shahar-Kashtan | CC BY-SA 3.0 |
edited body
|
| Jul 6, 2013 at 18:59 | history | answered | Avner Shahar-Kashtan | CC BY-SA 3.0 |