For components that are not provided via the toolbars, there is no reason to test them in a separate directory.
|I place the component source in the root of the structure. This also includes custom image and resource files - as appropriate. It would also make sense to place these in a directory called "source".
|These are the forms used to develop the component. Some use the path to
access the new component.
My Vista form repair component required 6 different forms to develop it.
|None of these use the path to access the component. Because my Vista form repair component modified the form at design time, it required 9 different forms to test it.
|This contains design notes, detailed instructions on how to test the component, and actual help files - currently written in html.
|Components on a toolbar need an icon (*.bmp). Some components also need screen shots or other images to document how they work.
|When producing html help files I keep them in under development until they are completed and spell checked. My standard configuration has several template files to help produce consistent results.
|These files are in html. I keep them in under development until they are completed and spell checked. As a result, each directory has its own images directory. Most components won't have web help.
|I provide separate directories for the packages (and compiled files) - one per version.
|I haven't found a content management system that I like, therefore I make periodic backups of the source files - pas frm bmp. Each subdirectory is named for the date of the most recent file it contains - yyyy-mm-dd.
I keep the help images in separate directories - adding additional subdirectories as appropriate. Because of how the help is partitioned, this requires a minimum of 4 directories.
In some cases, each of the main directories - help, testcases, and the like - will have its own backup directory.