Re: Project Folder Structure
From: J French (erewhon_at_nowhere.uk)
Date: 10/30/04
- Next message: J French: "Re: Replace Internet Transfer Protocol"
- Previous message: Sparko: "Password recovery"
- In reply to: Tod: "Project Folder Structure"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 30 Oct 2004 13:06:03 +0000 (UTC)
On Fri, 29 Oct 2004 07:02:34 -0700, "Tod" <todtown@swbell.net> wrote:
>I've been creating Excel reports for a few years, but
>have now inherited a server with a bunch of VB 6.0
>projects. It's a real mess. Files are strewn about all
>over the place with no real regard as to what goes where.
>Modules are FULL of sloppy code and tons of commented old
>code.
>
>I'm going to take on the task of deleting projects they
>don't need and cleaning up the ones they do need. I know
>the language fairly well from using VBA, but am not too
>aware of the best way to structure the files associated
>with each project. Most of the projects that I'm keeping
>use the same modules. I'm thinking of putting those
>modules in one folder for each project to reference.
>Also, the standard executables from these projects are
>used in Scheduled Tasks. I'm thinking I could put all of
>the EXEs in one subfolder. Then create separate folders
>for each VBP and related files. Does this sound about
>right?
I strongly recommend that you back up thoroughly first.
Each project has a .VBP file which contains the file names of all
modules used in the project.
Annoyingly these can be very 'relative' eg: ..\..\dir1\module.bas
If you are dealing with a really messy programmer then there could be
multiple modules with the same names but very slightly different code.
There could also be 'cross-links' all over the disk.
If the EXEs belong in the same suite, then, yes they should be in the
same directory, but I expect there will be more than one suite of Apps
on the machine.
My preferred setup is:
x:\dev\uslib ' modules used by /everything/
x:\dev\app1 ' standalone App source & exe
x:\dev\app2
x:\dev\suite1 ' exes for the suite in here
x:\dev\suite1\common ' modules common to suite1
x:\dev\suite1\appA
x:\dev\suite1\appB
x:\dev\suite1\appC
If you have large Apps - or rather Apps with many modules, then it
could be an idea to programmatically move them around
- or hunt for a utility to do that for you
Manually moving Apps from within VB is time consuming, easy to screw
up and thoroughly unpleasant as 'real' file names and paths are
inconveniently obscured from the programmer.
Personally I would programatically collect and analyse the .VBP files
before doing anything else.
Also watch out for things like .FRX files and possibly resource files.
- Next message: J French: "Re: Replace Internet Transfer Protocol"
- Previous message: Sparko: "Password recovery"
- In reply to: Tod: "Project Folder Structure"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
