Installshield 2012 registering a dll in the Custom Actions During Installation

What you want to do is set that DLL as the key file for a component and set it up to register the COM at install time.  No custom action should be needed.  There are a couple of ways to do it depending on project type and DLL.

here are a couple of links to get you going, Flexera will have more info on their pages as well.

http://www.installationdeveloper.com/3028/com-extractionregistration-in-an-installshield-project/

http://helpnet.flexerasoftware.com/installshield17helplib/IHelpCompRegSelfReg.htm

I'm learning each time I look at this. Thank you for the link, but it appears those procedures are for DLL created with source code. I did forgot to mention that this DLL I'm trying to register is a third party so I cannot build it to produce the key file.

You don't need to have authored the file to set the COM properties in Installshield.  Setting it as a key file of a component simply tells Installshield that it is the "important" file and uses that file when performing the various actions (COM, Gac etc) on that component in Installshield.

http://helpnet.flexerasoftware.com/installshield17helplib/IHelpCompRegDynamic.htm

Another link to help out.

Having  hard time following any of the methods for DLL registration outlined in either of the above links. None of the screen shots are familiar with InstallShied Express 2012.

Here is a link to info about IS12 Express specifically, I unfortunately do not have that version installed but the process should be similar.

http://helpnet.installshield.com/isxhelp18/IHelpISXComReg.htm

Essentially, you need probably want to be in their "advanced view" not the super simple wizard view they try to default to.  Make sure your DLL (the one needing to be registered) is in a component by itself, set as the key file.  Once on that component, there will be options for the COM settings and other things.

OK, I can get as far as what's described in the previous link but were I fall off is where you describe "Make sure your DLL (the one needing to be registered) is in a component by itself". What are you calling a component?

It's a basic installshield building block, a way to organize your Installshield project.  if you're in their "advanced" view (I think they call it the installation designer) and look for the "Setup Design" node in the tree.

under that you will see one or more "Features" which look like little pie charts in all versions of IS I have used.  under each of those you see one or more "components" which look like folders with a sheet of paper on them.

Basically, each component has settings for how to treat the files or file in them.  In order to meet strict windows validation, this often means one file per component.  that's not always needed though, as long as you set a key file properly it is typically ok to have multiple files in one compoenent.

hope this helps.

Getting a little closer. In the below screen shot the dll I'm trying to register is in the Nuance Binaries feature. Just not sure where to go to get to the file and right click to see the "Key File" option.

That's a bit different layout than the versions I use...but my best guess is you will find it under the Files and Features node down under the Specify application data node.

Why they (Installshield) can't be consistent is beyond me...

Not sure the Express version allows this. I get to the file and right click and my only options are "Remove" and "Copy".

try clicking the files node under the set application files, then right clicking on the file you need to register and going to properties...hopefully you will see the COM settings there.  if not, I am at a loss without having the app installed here.

OK, that's were I was in following the procedures for the last link you set.

The what is the next step?

That depends on the DLL...if it is a .net file, they you'll need to set the .Net specific info there.  Typically what you have there is good, other than probably checking the COM interop flag on.  You can tell pretty easily if the COM interaction works after a test install.

Then that is all I need? I can just build and install and that dll will get registered?

thanks, I'll test tomorrow.