I am asking more of a fundamental questions which might sound rather obvious. What is the logic to decide that we should create multiple class library projects in a solution?
For e.g: I am planning to create a application for a client, which is like a ERP and would have multiple modules like Inventory, Purchase, Sales, Accounting, Manufacturing, CRM, etc. Now, there are two ways through which i can design the solution.
First is create a Solution in .NET and add class library project for business logic and website project for each of the module for UI.
Or
Secondly, create multiple solutions for each of the module and each solution would have two project, one class libary for Business logic and one website project for pages.
Now, i am not sure which one is right and what are the deciding factors on which we decide whether to go with option 1 or 2. DO let me know if there are some better option as well.
TusharDave
0 Points
2 Posts
How to decide that multiple class library projects are required.
Feb 16, 2012 07:21 AM|LINK
Hello Friends,
I am asking more of a fundamental questions which might sound rather obvious. What is the logic to decide that we should create multiple class library projects in a solution?
For e.g: I am planning to create a application for a client, which is like a ERP and would have multiple modules like Inventory, Purchase, Sales, Accounting, Manufacturing, CRM, etc. Now, there are two ways through which i can design the solution.
First is create a Solution in .NET and add class library project for business logic and website project for each of the module for UI.
Or
Secondly, create multiple solutions for each of the module and each solution would have two project, one class libary for Business logic and one website project for pages.
Now, i am not sure which one is right and what are the deciding factors on which we decide whether to go with option 1 or 2. DO let me know if there are some better option as well.