>>>>Just one more little thing to clarify on the topic of Interfaces. I know now that I need to keep them in a separate project. And then reference the assembly of this project in those classes where the interfaces are used.
>>>>
>>>>So I will create a project MyInterfaces in the MyCompanyFramework Solution Folder.
>>>>
>>>>But my question is, is it a good practice to create a separate project for Interfaces of different layers of the application? E.g. UIFormsInterfaces, BIZInterfaces, DALInterfaces. Or simply keep all interfaces in one project?
>>>>
>>>>Again, thank you for any suggestions.
>>>
>>>
>>>I do not think that each set of interfaces have to go in a separate project/ assembly
>>>
>>>The Form interfaces can go in the project that contains the form (base) classes
>>>
>>>I would not keep all interfaces in one project
>>
>>Gregory,
>>
>>First, thank you for your suggestion. But it is a little confusing. In the first sentence you say "not to put each set of interfaces in a separate project" And then you say "would not keep all interfaces in one project". These are (IMO) to contradicting statements, no?
>
>
>Yes, seems contradicting. Should have structured my answer better
>
>
>The last answer was answering your last question (Or simply keep all interfaces in one project?)
No problem. Thank you Gregory.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
