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.
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


I never trust the self reg table - cant you just drop it from there?

How odd you have a score of -1
Answered 04/27/2007 by: fuz_kitten
Second Degree Blue Belt

Please log in to comment
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.

ORIGINAL: fuz_kitten

How odd you have a score of -1

FFFFFFFFFFFFFFFF sounds so much more .. erm .. positive [;)]

Answered 04/27/2007 by: spartacus
Black Belt

Please log in to comment
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. .
Answered 04/29/2007 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment