Last post Aug 03, 2016 01:17 PM by enendaveyboy
Aug 02, 2016 12:59 PM|EnenDaveyBoy|LINK
I have a project which has a core, data, service and presentation layer (asp.net mvc), and I am building a cms now I am building the front when which at present has the same setup but different service and presentation layers, however some but not all of
the service cross over, so would be ok to have differen projects for many of the services? and if so are there any downsides to having a larger number of sepate projects? and although I am the only developer at the moment wil it make any difference to having
Any information appriciated.
Aug 02, 2016 04:04 PM|Mikesdotnetting|LINK
One reason for having code in separate projects is so that multiple developers can work on separate aspects at the same time. The data access person can check that project out and work on it without stopping the UI person from doing what they need to do.
Another is so that code can be reused across multiple applications, but maintained in one location.
One downside is having to remember where you put stuff - especially if the namespaces you use don't align with the project/assembly names.
Aug 03, 2016 01:17 PM|EnenDaveyBoy|LINK
Thanks for the clarification good to know its the way to move forward.