[dba-VB] Multi-project solution

Michael,

It's not so much the using / references as having a copy of all of the properties in each project.

I originally developed the code directly on the server.  I used remote desktop to log in, it was 
just me, everything is "fine".  Then I hired a fine fella to help me, and started trying to get 
organized.  Set up a workstation for him, started getting the whole thing running from the 
workstation.

Now the code running from either workstation takes about 10 times as long to compile ( a couple of 
seconds directly on the server... that long for EACH PROJECT on either workstation.  You can 
actually watch it compile project by project.  That isn't huge, it just takes 15 or 20 seconds to do 
a compile now instead of 2 or 3.  However...

Debug takes about a second or two PER STEP on the workstations.  No se por que.  However when I 
Google that I get a TON of hits.  With a TON of DIFFERENT "go into the project / properties / 
somespecifictab and look for...".  Well guess what, I now have a half dozen projects to do this with.

That SUCKS!  I haven't found the fix, but I have spent a TON of time going in time after time, 
project after project searching through the properties stuff to see if I have the specific fix that 
worked for developer XYZ.

It is waaaay more than just a reference and a using...

I can see how projects would be cool if they are going to be pieces of many different solutions, 
however mine aren't, they are just an organizational tool for my single solution.  And yes, they 
make organization neat however there is a rather large price IMHO.

John W. Colby
www.ColbyConsulting.com


Michael Maddison wrote:
> Hi John,
> 
> I think it's you bud :-)
> I think most people quite like compartmentalising their code using
> projects and NameSpaces. 
> Adding a ref or Using is a small price to pay IMO.
> 
> If your project is an internal project for your DBFH then 1 solution and
> 1 project is probably fine for you.
> However, I'd still break it down using namespaces, something like... 
> 	Colby.DBFH.Forms
> 	Colby.DBFH.Data
> 	Colby.DBFH.Data.Services
>  	Colby.DBFH.Data.Entities
> 	Colby.DBFH.Data.Providers
> 	Colby.DBFH.Tools
> 	Colby.DBFH.Settings
> 
> 
> Each namespace can be it's own project or all mixed together any way you
> like. Put your classes in the appropriate namespaces and
> as the solution grows you will be able to keep organised. (and it looks
> nice in object explorer)
> 
> 
> HTH
> 
> Michael M
> 
>  
> 
> 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?
>