Software Deployment

Ankit,

The Practise i used to follow is capture the source, keep it aside for ur reference.

Capture the different registration entry with follwoing method.

<Full Path of "WiseComCapture.exe" File on ur machine> <Full path dll / ocx> <Path of reg file>
This shoud be done on the machine where you have capture the MSI & all the files are regisetered.
This will give you registration information of perticuler files, then import it in ur MSI with Advertising information in advertising tables.

Regarding Error 1911 for typelib, it may be the case that perticular file dont have Typelib information itself, that is the case then no need to keep that perticular typelib entry in the package.

Hope this will help you.

Cheers
Jimit

Error 1911 means that an attempt to register one of the files failed. If it is a Type Library it may have a corrupted entry in the typelib table. This sometimes manifests itself as an odd number in the language column. You can try deleting the row from the table that references the file and see if the app still functions. If not you can use a utility like regtlib.exe in a custom action to register the library instead of the regtlib table.

On incorrectly coded .DLL files wise will sometimes read them as self registering even when they are not. In those cases it is acceptable to turn off the self register flag in wise. Other times however a library wont register because it is in the wrong order and has a dependency on another library that hasn't been registered yet. In that case you will need to enable ordered registration. Testing will help you determine which case you have.