Removing Self Reg Information Captured
Hi Everyone ,
I am facing a peculiar problem while package creation, According to our client the package should self register the dlls/ocx that it can do at runtime.The problem during setup capture ( Using Wise Package Studio) the registry information also gets captured. Its taking a lot of time removing this registry from the registry hive , as we dont want any redundacny(Since the dll/ocx has to be put in self reg table ). Any suggestions/comments to speed up this manual searching and removing registry process.
I am facing a peculiar problem while package creation, According to our client the package should self register the dlls/ocx that it can do at runtime.The problem during setup capture ( Using Wise Package Studio) the registry information also gets captured. Its taking a lot of time removing this registry from the registry hive , as we dont want any redundacny(Since the dll/ocx has to be put in self reg table ). Any suggestions/comments to speed up this manual searching and removing registry process.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
fuz_kitten
17 years ago
I never trust the self reg table - cant you just drop it from there?
How odd you have a score of -1
How odd you have a score of -1
Posted by:
spartacus
17 years ago
Have you checked the setup capture configuration in WISE Package Studio - specifically Advertising Setting ?
It's a while since I last used WPS but I believe if this setting is currently set to "Retain registry information as-is" then the capture won't attempt to use the Advertising-related tables (where possible) and just dump everything into the Registry table.
I agree with fuz_kitten that the SelfReg table can cause problems. If you set the Advertising Setting to "Convert registry entries into advertising info" then WPS should attempt to move as much of the registry information into the various COM tables - anything it can't resolve will be left in the registry table.
FFFFFFFFFFFFFFFF sounds so much more .. erm .. positive [;)]
Spartacus
It's a while since I last used WPS but I believe if this setting is currently set to "Retain registry information as-is" then the capture won't attempt to use the Advertising-related tables (where possible) and just dump everything into the Registry table.
I agree with fuz_kitten that the SelfReg table can cause problems. If you set the Advertising Setting to "Convert registry entries into advertising info" then WPS should attempt to move as much of the registry information into the various COM tables - anything it can't resolve will be left in the registry table.
ORIGINAL: fuz_kitten
How odd you have a score of -1
FFFFFFFFFFFFFFFF sounds so much more .. erm .. positive [;)]
Spartacus
Posted by:
jmcfadyen
16 years ago
sounds to me like you need to be educating you client on this.
self registration is great for a single app no good for an enterprise. .
self registration is great for a single app no good for an enterprise. .
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
