[dba-VB] Multi-project solution

jwcolby jwcolby at colbyconsulting.com
Fri Jun 11 15:24:12 CDT 2010

I launched in to building a C# application where I divided the solution into projects.

It certainly seems to make sense, a solution can have multiple solutions, and each solution becomes 
an arm in a tree structure inside of the solution.

OTOH each project has an entire set of properties all it's own.  They are not inherited from parent 
(solution) properties.  I don't claim to be any guru but it sure seems that many of the properties 
in the project really should apply to the entire solution.  For example each project has a 
properties.Settings.  However there is no Solution.properties object at all AFAICT, never mind a 
Solution.Properties.Settings.  Thus (for example) I have a server name, a bunch of paths on the 
server etc.  All of those things have to be declared over and over in each project's 
Properties.Setting or... have to be declared in one specific project and then that project 
referenced in every other project.

Is it just me or is this project thing a lot of extra effort for what you get?  What specifically DO 
you get?

John W. Colby

More information about the dba-VB mailing list