AA wrote:
I am adding a COM reference to my VB.NET project. On adding that
reference X, in the references section I get the reference name as
Interop.X with type COM and path as /obj/Release/Interop.X.dll.
I wanted to know how this dll gets generated.
That's the Visual Studio IDE doing the work for you and, so long as this
use of the COM component is a one-off, it's probably Good Enough.
However, you might also want to look at the Tlbimp utility, that creates
the InterOp assembly from on a Type Library, and has some useful options
like Strongly Naming the InterOp assembly so that you can add it to the
Global Assembly Cache, rather than having a separate InterOp Assembly
for each application.
HTH,
Phill W.