TLB to managed .NET assembly without Regsrv32 at deploy time

后端 未结 2 1883
予麋鹿
予麋鹿 2021-01-22 15:33

I have a TLB that was provided as a part of a third-party API. I used TLBIMP.exe to generate a DLL assembly wrappper. However, at development time, it appears that the assembly

2条回答
  •  野性不改
    2021-01-22 16:23

    Sadly, no. Your target DLL is a COM DLL, and as such, must be registered on each box it's deployed to. The good news, assuming you're building an installation package for deployment, is that most installer toolsets worth their salt should support COM registration out of the box. Check your installer's documentation.

    If you're deploying via xcopy to a large number of boxes, I'd say it's time to rethink your strategy. The only comfort you might take in this is that a COM DLL only has to be registered once per box, per version deployed. But still, xcopy installs are generally a bad idea these days.

    UPDATE: I stand corrected -- I'm voting up Noseratio. Shows how little I pay attention to COM integration these days.

提交回复
热议问题