I'm a Newbee, so maybe this question was posted before.
I do repackaging an IS file with Wise and get hundreds of registry entries like this:

[HKEY_CLASSES_ROOT\Interface\{01A21FB9-74F1-4934-81F0-8C473F7A6E50}]
@="ICustomization2"

[HKEY_CLASSES_ROOT\Interface\{0225839A-79F8-4493-872C-004FFDDF0CA1}]
@="IBaseHierarchyTreeManager"

[HKEY_CLASSES_ROOT\Interface\{025854DA-9D81-40E8-853D-F4EA33073A77}]
@="IRecordset"

[HKEY_CLASSES_ROOT\Interface\{03986C41-712B-4A6F-8C65-B50CBF7FC640}]
@="ISearchableFactory"

[HKEY_CLASSES_ROOT\Interface\{05518018-2339-4E08-87BE-D14C69527B7A}]
@="ICustomizationReqType"

I wonder why they all have an "I" at the beginning. Are they useful for the application or is it something from IS that is not necessary for the application itself? Does anybody know something about this?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
The "I" indicates the Class is an Interface.
They could be part of the InstallShield engine, ISScript.msi or legacy.
You would need to verify if the Interface is used by the IS engine or not.
If not then keep them.
Answered 11/14/2007 by: AngelD
Red Belt

Please log in to comment
0
Forgott that you can use my "CleanOutInstallShieldRuntimeRegistry.vbs" found at below thread to get all related IS registry entries that could be removed from the MSI if included in the capture.
http://itninja.com/question/migrate-2000-professional-workstation-snmp125&mpage=1&key=&#28125
Answered 11/14/2007 by: AngelD
Red Belt

Please log in to comment
0
Somewhere there's an INI section you can paste into Repackage.INI (local) or WisePSSC.INI (global) to set Wise to ignore InstallShield registry stuff.
Answered 11/14/2007 by: VBScab
Red Belt

Please log in to comment
0
This is an old thread, but here's a handy little tip:

%Systemroot%\WisePSSC.ini: This is the local exclusion list file that Wise always checks first during a SetupCapture --even before the share-based Repackage.ini. To avoid file/version conflicts, I'd recommended no entries aside from the redirect to “network”, which forces Wise to use "master" Repackage.ini on the Wise Share Point:
[Manager]
Config Location=Network
Answered 08/31/2009 by: norexx
Orange Belt

Please log in to comment
Answer this question or Comment on this question for clarity