Software Deployment

The only other reason I've heard of is purely for 'neatness' i.e. it can make it easier to manage the data if it is split up into categories instead of all being lumped together in the one table. I think it's a lot of work to shift information from the registry table to the class tables etc manually so I just rely on my repackager tool to do the work, which it does well for the most part. Occasionally it may omit to delete duplicate information from the registry table during conversion, which can lead to the classic ICE33 warnings.

Alan

Cheers mate.

Further to my question, can anyone explain exactly how self healing could be triggered via COM registry entries generated by the Class table?

Is it as simple as populating the table, and if an application calls the DLL etc it acts as an entry point?

ORIGINAL: OldWiseMan
Is it as simple as populating the table, and if an application calls the DLL etc it acts as an entry point?

That's how I understand it. As the class table references the component that installs the file instead of the actual file itself, it acts as an entry point for the advertising.

Alan