56 reputation
1
bio website igloocoder.com
location
age
visits member for 2 years, 8 months
seen Jan 2 at 16:32

Apr
20
comment Layers - Logical seperation vs physical
About the friction on build script mgmt, my projects rarely have any. I find that once the base build script has been completed (usually early in the project), I only make minor modifications to the script and then only every few months. One of the keys to doing this is structuring your subfolders (logical layers) well and keeping the code within them highly decoupled. If you do that, you can simply change the script to (pseudo code here): - include MyCo.MyApp.Service*.cs - include MyCo.MyApp.DAL*.cs It makes splitting out, or adding in, a logical layer from an assembly is quite easy.
Apr
20
comment Layers - Logical seperation vs physical
What I usually end up with is about 2-5 *proj files on a project (depends on a number of bigger architectural things like needing Windows Services, console batch programs, ect). Usually there is 1 main proj and in it I subfolder it at a logical level. So there would be a subfolder each for View, Dto, ViewModel (in a WPF app), Services, Repositories, etc. I use my build script to create the assemblies I need. If I want to start with UI.exe only, then I do. Later I can pull things off to create UI.exe and Backend.dll. That change doesn't affect the *proj file contents or structure.
Apr
20
awarded  Teacher
Apr
20
answered Layers - Logical seperation vs physical