Hello, I have a fairly clean ASP.NET MVC project structure. However, I'm struggling on how to organize the mass of classes which are DTOs (data transfer objects), e.g. just to encapsulate post data from forms (viewmodels) but don't represent full domain objects or anything near that yet; and then the many "result" objects I have which c...
Hello, I'm looking for multiple inputs on great project organization/structure, preferably especially for complex ASP.NET MVC projects (which will definitely go beyond the couple of folders initially created by the project type). Project organization also includes topics like naming conventions, lumper/splitter preference on classes, ...
Are non-data classes (that are not representing anything in the database) still considered a part of an application's domain model or not? Would you put them together with your Linq2Sql domain model or somewhere else?? Edit: Info about classes: For example, I have a "StatusMessage" class which is instantiated under certain circumstances...
At top there is some most useful info about foo. Between horizontal lines there is some immediate actions, if they are available, to perform on/with foo. And below is thing that bothers me. There goes tabbed, detailed information about foo. Those tabs can hold some actions too and can be quite sovereign. So the question is - how ...