Home/ Questions/Q 7046799
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T02:41:37+00:00

Situation I run a build system that executes many builds for many project. To

  • 0

Situation
I run a build system that executes many builds for many project. To avoid one build impacting another we lock down the build user to only its workspace. Builds run as a non privileged users who only have write ability to the workspace.

Challenge
During our new build we need to use a legacy 3rdparty DLL that exposes its interface through COM. The dev team wants to register the build(regsrv32.exe) but our build security regime blocks this activity. If we relax the regime then the 3rdparty DLL will impact other builds and if I have two build which need two different versions I may have the wrong build compile against the wrong version (a very real possibility).

Question
Are there any other options besides registration to handle legacy DLLs which expose their interface via COM?

Thanks for the help

Peter

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    There’s a walkthrough on registration-free COM here:

    http://msdn.microsoft.com/en-us/library/ms973913.aspx

    And excruciating detail here:
    http://msdn.microsoft.com/en-us/library/aa376414
    (the root of that document is actually here: http://msdn.microsoft.com/en-us/library/dd408052 )

    Also, for building in general, you should be able to use Tlbimp or tlbexp to create a TLB file that you can use for building, assuming the point of registering is just to be able to compile successfully, and not to run specific tests.

    • 0