Hi,

I am having one small doubt. According to the microsoft best practices, we should not have self reg entries in the package instead they should be registered and added in the package.

But I want to know why we should not have self reg entries. If we have self reg entries in the package what will happen. Since I checked one vendor msi it is having self reg entries and during installation it is not showing any pop ups releated self reg entries. And the installation happened fine.
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
If there's one lesson to learn here, it's that you should never use vendor MSIs as any guideline on how to package properly.

For me, the biggest single reason to not use self-registration is that your package may then rely on the presence of dependencies. That is to say, if a DLL/OCX has a dependency which isn't present on the target, self-registration (or the even worse route, a CA calling RegSvr32 or MSIExec /y) will fail.

And BTW, there's no need to shout :)
Answered 11/19/2009 by: VBScab
Red Belt

Please log in to comment
0
Clean Uninstalls?
Answered 11/19/2009 by: nissel
Yellow Belt

Please log in to comment
0
Yes, As per my knowledge, Rollback of an installation with self-registered modules cannot be safely done using DllUnregisterServer.
Answered 11/19/2009 by: sanhivi
Second Degree Green Belt

Please log in to comment
0
You will find, lot of information on Appdeploy related to this topic. Just search...
The main reason between, self registration, and adding advertising registries in the package is,
"Self registration means, at the time of installation, it will use regsvr32.exe to register files, as well as registration will be depending upon dependencies as told by vbscab. Using regsvr32.exe is same like you register it manually. Only difference will be same command will be executed through selfreg tables. So Microsoft does not guarantee you, that at the time of uninstallation or rollback, all the registered dlls will be un-register successfully. If you import advertising registries then you will get a prompt to import them through proper advertising tables. You need to select 'yes'. So these advertising registries will be like a part of that msi databse, so even at the time of failures, rollback, uninstallation, things will work fine"
Answered 11/19/2009 by: Yaduveer
Orange Senior Belt

Please log in to comment
0
do a search lots of info and dicussions, scripts and codes etc on self reg malakee
Answered 11/19/2009 by: cygan
Fifth Degree Brown Belt

Please log in to comment
0
Self registration means, at the time of installation, it will use regsvr32.exe to register filesNot quite. In fact, for entries in the SelfReg table, the WI engine uses the Windows API DLLRegisterServer to register DLLs/OCXs since it itself couldn't guarantee the presence of RegSvr32.EXE. If you import advertising registries then you will get a prompt to import them through proper advertising tables. You need to select 'yes'That, of course, only applies to Wise Package Studio users.
Answered 11/19/2009 by: VBScab
Red Belt

Please log in to comment
0
Opologies for that statement :)
Answered 11/19/2009 by: Yaduveer
Orange Senior Belt

Please log in to comment
0
No need to apologise! :) All of us are learning something every day.
Answered 11/19/2009 by: VBScab
Red Belt

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