[dba-VB] Multi-project solution

Michael Maddison michael at ddisolutions.com.au
Fri Jun 11 23:17:35 CDT 2010




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 

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.  

>>> You can set the build properties of each project in the solution.
Right click on Solution -->
Configuration manager --> untick the projects that don't require
building each time you run the solution.


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.

>>> I can't say I've had to do more than run with the defaults. 

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

>>> It seems you are developing on code shared from the server? Is that
right? I can't help with that
other to advise setting up Subversion and developing locally. Am I
missing the point?

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.

>>> Yes but, disabling build on the projects that are stable will speed
build up a lot.
>>> Working on local working copies of the code will speed up debugging,
I'm pretty sure.


Michael M

John W. Colby

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
> 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
> like. Put your classes in the appropriate namespaces and
> as the solution grows you will be able to keep organised. (and it
> nice in object explorer)
> Michael M
> I launched in to building a C# application where I divided the
> 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
> each project has a 
> properties.Settings.  However there is no Solution.properties object
> all AFAICT, never mind a 
> Solution.Properties.Settings.  Thus (for example) I have a server
> 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
> 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?
dba-VB mailing list
dba-VB at databaseadvisors.com

No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 9.0.829 / Virus Database: 271.1.1/2928 - Release Date: 06/12/10

More information about the dba-VB mailing list