Hi,
I have some C++ native clients that need to interact with managed assemblies
for which there are existing idl files (these assemblies are migrations from
C++ to C#).
The C++ clients use idl files to build the .tlh and tli files so they can
interact via COM with the assemblies.
Using #import is unnecessarily large since only one interface is desired.
Also, the interface desired will not change whereas the assembly will thus
producing unnecessary dependencies which will force my C++ clients to
recompile each time the assemblies change even though the interface used by
the clients will never change.
This has prompted me with the question as to if it is possible to generate a
subset of the .tlb, which only includes the desired interface and which is
not sensitive to changes to the assemblies that implemented the interface.

Signature
Thanks in advance,
Juan Dent, M.Sc.
Robert Jordan - 18 Oct 2005 01:23 GMT
Hi,
> I have some C++ native clients that need to interact with managed assemblies
> for which there are existing idl files (these assemblies are migrations from
[quoted text clipped - 10 lines]
> subset of the .tlb, which only includes the desired interface and which is
> not sensitive to changes to the assemblies that implemented the interface.
You can open the TLB generated by RegAsm with OleView.exe and
save the IDL to a file.
Rob
"Peter Huang" [MSFT] - 21 Oct 2005 02:40 GMT
Hi Juan,
Did Robert's suggestion help you?
If you still have any concern, please feel free to post here.
Best regards,
Peter Huang
Microsoft Online Partner Support

Signature
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.