Defining Project Organization Standards

[SGLong]

Our development team is expanding and we've realized that we need to develop some in-house standards for how we organize our projects (directory structures, etc.). There are several styles that have been suggested - each having their plusses and minuses. One style is a separate directory for PRGs, one for Forms, one for Reports, one for Artwork, etc. Another style is one for the 'project', one for documentation, etc.

What are other development shops using and why?

Thanks

Steve

 

[BlindPete]

We follow one similar to the first one you described. I can't say it is best, I can't say it is ever let me down either. IMO it is much easier to make a project portable between programmers if all elements of the project (including user created classes) are contained in the ProjectFolder and its subs.


-Pete

 

[BlindPete]

In addition... I travel often. I like to be able to work on the software while on location. I hate using a laptop full time so I have a desktop in HQ. When I travel all I have to do is drag the projectFolder I'm working on to the laptop and I'm good to go.
-Pete