Our project has a number of dll and ocx files which are all registered. When I set their Auto register option to 'Extract registration info from native library' I noticed that their Registry Keys are all listed on the Organizations page, each key having their own Component.
With each dll/ocx file having between 40 and 100 keys that adds up to several hundred Components alone, is this association really necessary.
Wouldn't it be preferable if all keys for each file be under 1 Component for each file, labelling it with the file's name, possibly with a 'RegKeys_' or similar prefix or suffix.
While still in the Organizations page, files listed here are grouped in Components according to their folder, but the Component's name is generated from the top listed file. This is awkward for a Web application project when this file is usually either default.htm or default.ASP and thus most end up with the same name (besides the number suffix).
A better solution for the Component name would be to use a value derived from the Component Properties/ General/ Directory: value, I personnally use this and replace the (not accepted) back slashes with periods to visually preserve the folder structure.
Unfortunately the list of Components under each Feature does not reorder to display alphanumerically, this is another feature I am chasing.
These changes will eliminate time consuming manual restructuring and editing of names, and make Components quicker and easier to locate and work on. This will tidy up an already excellent product.