Sign In
Mason Bendixen's COM Interop Notes
Translate This Page
Translate this page
Powered by
Microsoft® Translator
Options
Email Blog Author
RSS for posts
Atom
RSS for comments
OK
Search
Advanced search options...
Search In:
Everything
Blogs
Forums
People
Groups
Places
Pages
Date range:
All Time
Last Year
Last 6 Months
Last 3 Months
Last Month
Last Week
Last Two Days
Tags
CCW class interface design dual interfaces dispatch interfaces generics
CoSetProxyBlanket runtime callable wrapper RCW
runtime callable wrapper RCW com interop
tlbimp type library com interop platform dependent
Archive
Archives
April 2007
(6)
April, 2007
MSDN Blogs
>
Mason Bendixen's COM Interop Notes
>
April, 2007
Posts
Subscribe via RSS
Sort by:
Most Recent
|
Most Views
|
Most Comments
Excerpt View
|
Full Post View
Mason Bendixen's COM Interop Notes
CoSetProxyBlanket not supported from managed code
Posted
over 5 years ago
by
MSDNArchive
1
Comments
COM objects are represented in managed code by runtime callable wrappers. I have written a reasonable summary of runtime callable wrappers (RCWs) here that you should read to understand the concepts in this entry. CoSetProxyBlanket is a useful API...
Mason Bendixen's COM Interop Notes
The mapping between interface pointers and runtime callable wrappers (RCWs)
Posted
over 5 years ago
by
MSDNArchive
2
Comments
The term COM object is frequently thrown around, but people really access interfaces off of objects. The objects themselves are hidden. Managed is quite a bit different since interfaces are part of the system, but people can also access objects directly...
Mason Bendixen's COM Interop Notes
ClassInterfaceType.None is my recommended option over AutoDispatch & AutoDual
Posted
over 5 years ago
by
MSDNArchive
1
Comments
Advanced to intermediate COM programmers are well aware of the problems with dual interfaces. I won’t discuss that here, but people should read Don Box’s book Essential COM if they want an excellent explanation of this. There is a good discussion of avoiding...
Mason Bendixen's COM Interop Notes
A single Interop assembly does not work for different architectures
Posted
over 5 years ago
by
MSDNArchive
1
Comments
One of the exciting things about managed code is that it is quite a bit easier to write code that is portable across architectures. There is no question about the size of a short, int, or long integer. In fact, it is possible to write assemblies that...
Mason Bendixen's COM Interop Notes
Non-Cocreatable Class Objects No Longer Wrapped in NDP 2.0 and Later
Posted
over 5 years ago
by
MSDNArchive
5
Comments
I dealt with a customer attempting to automate Microsoft Outlook 2003 using the Outlook Primary Interoperability Assembly (Microsoft.Office.Interop.Outlook.dll) for the Microsoft Outlook 11.0 Object Library type library version 9.2. The type library...
Mason Bendixen's COM Interop Notes
Mismatch between object lifetime when bridging between COM and managed code
Posted
over 5 years ago
by
MSDNArchive
1
Comments
From time to time, I see object hierarchies like: interface IParent : IUnknown { [propget] HRESULT Child([out, retval] IChild ** ppChild); } dispinterface IChildEvents { // ... } interface IChild : IUnknown { } coclass...
Page 1 of 1 (6 items)