• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 449
  • Last Modified:

Register COM with Limitied

I've just switched from VS's setup project to InstallShield Limited (VS2013) , I have a COM dll which needs registering, in the old VS I had 'Regiser - vsdraCOM option' which seemed to do the trick, now I just get COM - 'Self-Registration', or 'Extract COM Information' neither of which quite looks like 'Register', and indeed neither seem to register the DLL.
Anyone know how you're supposed to register COM DLL's?
0
Silas2
Asked:
Silas2
  • 4
  • 3
1 Solution
 
Vadim RappCommented:
The recommended way is not to self-register, but to extract COM information from the dll, and make that information part of the installation, pretty much like any other registry entry.* In VS's setup project this is accomplished by property Register=vsdrfCOM (not vsdraCOM). In Installshield the same is accomplished by "Extract COM Information".

You said that neither seem to register the DLL. What's the problem? give the details.

*) Simply speaking. In fact, support of COM registration in Windows Installer is much more extensive than just creating registry entries, but it's all "under the hood".
0
 
Silas2Author Commented:
Thanks for that explanation. I've got a COM interop component (3rd party), which comes with a .reg file, do you think I have to manually add each reg entry from that file to the 'Registry' node in the InstallShield/Solution explorer?
0
 
Vadim RappCommented:
> do you think I have to manually add each reg entry from that file to the 'Registry' node in the InstallShield/Solution explorer

If it does not support something like "import reg file", then yes. "Full" Installshield can, but this one may be limited.

From my own experience, (1) installations created by S&D project in VS have always been very solid (2) all attempts of VS team to "partner" with yet another vendor, like Obfuscator, Crystal Reports, and now Installshield, have always been not to the benefit of Visual Studio, to put it politely. I would either stay with S&D, or learn to use WiX.
0
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

 
Silas2Author Commented:
I would either stay with S&D, or learn to use WiX.
I am starting to agree with you...
0
 
Silas2Author Commented:
Hi, I'm not sure if this is in the same topic, but I have a customerinstall.exe (from the 3rd party), and I've added it to an installer class (crudely):
      System.Diagnostics.Process.Start(sipVoipInstaller, "/S /D=" + this.Context.Parameters["AssemblyPath"]);

Open in new window

, but on  Windows 7 I'm getting a registry access complaint as if this 'out-of-process' call doesn't have the same permissions as the rest of the install, but is ok for Win8 + XP????
Any ideas how to run the Process.Start so the started process has elevated permissions?
0
 
Vadim RappCommented:
> Any ideas how to run the Process.Start so the started process has elevated permissions?

No. I would repackage that 3rd party install (but I have the tools).
0
 
Silas2Author Commented:
I'm just living with it...its not very pretty but there's only a tiny bit to do manually and it's not got a very wide distribution.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now