By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,024 Members | 2,027 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,024 IT Pros & Developers. It's quick & easy.

Using third-party control in unmanaged code using CCW

P: n/a
Hi

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
stuck.

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.

Tim

PS. Here's what Microsoft say:

http://msdn.microsoft.com/library/de...ce11012001.asp

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
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.