By splitting functionaility into modules, it'll be easier for me (and any future developers) to easily find code relating to specific features of FarmMaster.
This also sets the groundwork needed for third party extensions, something Andy's expressed interest in. Although there's definitely still more work to be done before that can become a reality (where are the binaries stored, how do you get them, is there a manifest file, should shared dependencies be loaded multiple times, etc.)
If nothing else, researching on the topic and then implementing it has saved a few days of boredom, for hopefully little cost, and decent long-term benefit.
The two biggest annoyances in terms of development are:
Remembering to rebuild the project every so often, since sometimes outdated stuff gets used.
Razor template runtime recompliation eats even more memory than usual, and will run everytime a view is used for the first time per run (debug mode only though, so release mode is safe).
By splitting functionaility into modules, it'll be easier for me (and any future developers) to easily find code relating to specific features of FarmMaster.
This also sets the groundwork needed for third party extensions, something Andy's expressed interest in. Although there's definitely still more work to be done before that can become a reality (where are the binaries stored, how do you get them, is there a manifest file, should shared dependencies be loaded multiple times, etc.)
If nothing else, researching on the topic and then implementing it has saved a few days of boredom, for hopefully little cost, and decent long-term benefit.
The two biggest annoyances in terms of development are:
Remembering to rebuild the project every so often, since sometimes outdated stuff gets used.
Razor template runtime recompliation eats even more memory than usual, and will run everytime a view is used for the first time per run (debug mode only though, so release mode is safe).