Can any one plz answer my question

3 Comments   [ - ] Hide Comments


  • What mechanism are you using to deploy with?
    You've tagged 'Scripting', 'Virtualization', 'Package Development' and 'Software Deployment' for this post - each technology may have a different approach to take.

    For example, if it's an MSI you could extract the COM information and import to the registry of your package, you could tell your packaging tool to extract the COM information at build time or there are mechanisms in certain tools to self-register the files.

    Please provide further information about your situation and what you are trying to achieve and someone will be able to assist further.
  • I'd also be curious as to why you want to avoid using Regsvr32....is that approach limiting what you are trying to do, or causing some other problem?
  • Avoid using RegSvr32 if you're building the MSI yourself. Instead, as stated above, extract the COM information as .REG files and import those into your project, ensuring that the content gets put into the appropriate tables.

    Why? Because if any dependency is missing, Regsvr32 will fail. Of course, your testing ought to have identified the dependency and your package/deployment source altered accordingly.
Please log in to comment

Answer this question or Comment on this question for clarity



you could always capture the registry keys resulting from the dll registration and dump them on the target machine

Answered 07/25/2013 by: pjgeutjens
Red Belt

  • This content is currently hidden from public view.
    Reason: Removed by member request
    For more information, visit our FAQ's.
Please log in to comment

There are special sdk to achieve it e.g. Boxedapp sdk @ http://boxedapp.com

Answered 07/31/2013 by: ArtemRazin
Senior Yellow Belt

Please log in to comment