I am starting on a new project and wondered if I could get some ideas, suggestions, etc on how to structure the solution in Visual Studio - in terms of how (and how much) to split the code across different projects within the solution.
Currently, I have a project for the main Umbraco install, one for ModelsBuilder generated files, one for Core items (controllers, Migrations, Models, etc), then separate projects for things like AWS, API (for our app), Hangfire and for 3rd party systems such as GPS, Nuapay, Zoho.
So far, there are 16 projects within the solution (it connects to a number of 3rd party systems) but that is without any test project(s).
It seemed like a good idea while I was doing it, but now I'm wondering if I've broken it down too much!! :-)
It would be great to hear what other people do and what calls for a project of its own within the solution. Any links to videos or blogs on the subject would be most welcome.
Solution Project structure
I am starting on a new project and wondered if I could get some ideas, suggestions, etc on how to structure the solution in Visual Studio - in terms of how (and how much) to split the code across different projects within the solution.
Currently, I have a project for the main Umbraco install, one for ModelsBuilder generated files, one for Core items (controllers, Migrations, Models, etc), then separate projects for things like AWS, API (for our app), Hangfire and for 3rd party systems such as GPS, Nuapay, Zoho.
So far, there are 16 projects within the solution (it connects to a number of 3rd party systems) but that is without any test project(s).
It seemed like a good idea while I was doing it, but now I'm wondering if I've broken it down too much!! :-)
It would be great to hear what other people do and what calls for a project of its own within the solution. Any links to videos or blogs on the subject would be most welcome.
is working on a reply...