• Advertisement
Sign in to follow this  

Multiple Solutions

This topic is 3383 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

I was wondering if its "development savvy" to have multiple solutions in a development environment? This is an Engine, and the number of projects are growing fast, because of the number of Wrappers, Plugins, Utilities, ect... that i have. (right now i have around 13 - 15) Should i split them up into a Wrappers Solution, Plugins Solution, Utilities Solution, ect...?

Share this post


Link to post
Share on other sites
Advertisement
I would break them apart at the reusable functionality boundary (on the library borders) since that's what a solution means. But yeah, splitting things into libraries is good.

Share this post


Link to post
Share on other sites
Quote:
Original post by GanonPhantom
I was wondering if its "development savvy" to have multiple solutions in a development environment? This is an Engine, and the number of projects are growing fast, because of the number of Wrappers, Plugins, Utilities, ect... that i have. (right now i have around 13 - 15)

Should i split them up into a Wrappers Solution, Plugins Solution, Utilities Solution, ect...?


As long as it's practical to do so, keeping everything in one solution is nicely convenient.

Visual Studio doesn't scale *that* well with tons of projects in a single solution, but you'll notice when it starts getting unbearably slow... ;)

But until it becomes a problem for you (for performance reasons in VS, or because it otherwise gets in your way), there's no point in multiple solutions.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement