Reply to thread

Message: [QUOTE="Bob S, post: 9177177"] Is not always possible to have the interface in the shared assembly, because one .Net assembly may expose an interface (eg COM IDataObject) to the unmanaged world while another .Net assembly may consume the interface. Though the underlying interface is the same, .Net will not allow the casting. (In the case of IDataObject, this situation will not arise if you use the Microsoft defined type IOleDataObject - however this will not be possible for other interfaces). Thus .Net does not support the basic tenet of COM which says that COM is a "binary standard". It should not matter what the underlying ".Net type" of the interface is as long as the binary contract of the interface is the same. I think this is a serious flaw in COM support of .Net. I would love to hear some more views on this. Regards Bob Suppose assembly A exposes a COM IDataObject to the unmanaged world and defines [/QUOTE]