Projects structure
Some teams organize project items per tpye: a folder with the enums, another folder with the exceptions, another with the classes and so on…
I think that this is not the right way if you want a mantainable project, I think that should be better organize items based on context or application area that they belongs to. For example you should put all the items (class, enum, …) that are part of Order management in one folder (aka namespace) and in another folder the items that belongs to Invoicing.
This way the project is more modular and is quite easy extract a module in a separate assembly if it becomes necessary.
Posted in Emanuele DelBono | No commentsNo comments yet. Be the first.
Leave a reply
RSS
