Re: What makes VS2005 embed a type library in a DLL?
"Boris" <boris@gtemail.net> wrote in message
news:op.tt5ipdw545fww6@burk.t-com.ne.jp
On Tue, 19 Jun 2007 10:37:22 +0900, Igor Tandetnik
<itandetnik@mvps.org> wrote:
Do you have an attributed project, by any chance? See Project
Properties
Linker | Embedded IDL
Yes, it's an attributed project. Does that mean the type library is
automatically embedded?
Yes, as far as I can tell.
Or it is automatically embedded if the project
property "Type Library" is empty (as I didn't specify a name there)?
I believe it is irrelevant. If Type Library option is empty, a default
file name will be used, but the final TLB will be embedded in resources
anyway.
Ah, I see now that there is a "TypeLib Resource ID" property which is
set to 1. I guess that makes VS2005 embed the type library?
The use of attributes is what makes VS2005 embed the type library. This
property specifies which ID to assign to the resource. But it doesn't
look like there's any value you can give this property to _suppress_
embedding the TLB as a resource.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925