471,354 Members | 1,284 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,354 software developers and data experts.

Using third-party control in unmanaged code using CCW


Can somebody help me, please!

I'm trying to use a third-party .NET forms control in an unmanaged
COM-aware application (MFC).

I have no problem doing this with normal .net controls, as they conform
the requirements of a COM Callable Wrapper (CCW).

The problem I'm having with a particular third-party control, is that
it uses parameters in its constructor, which is a breach of the CCW
rules. I have thought about subclassing the control, but COM eventually
calls the default constructor, which I think is where I'm getting

Does anyone have an example of using a .NET control that requires
parameters to be passed to its constructor in an unmanaged (preferably
MFC) application?

Thanks in advance for any help/pointers with this.


PS. Here's what Microsoft say:


Go down to where it says
"Calling the .NET Framework Class Libraries from Office VBA"

It may talk about VBA rather than MFC, but the same rules apply, i.e.
COM calls the default constructor.

Jan 26 '06 #1
0 1293

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by johkar | last post: by
4 posts views Thread by Michael Hill | last post: by
12 posts views Thread by Jan Roland Eriksson | last post: by
6 posts views Thread by thesushant | last post: by
4 posts views Thread by dmeiser | last post: by
4 posts views Thread by not_a_commie | last post: by
reply views Thread by XIAOLAOHU | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.