Re: ATL in WinForms app
"Maxim" <vmu-at-mail-dot-ru> wrote in message
news:OIuydegnHHA.1904@TK2MSFTNGP02.phx.gbl
What for? ATL is normally used to implement COM objects. It is highly
unlikely that a managed object would provide a COM-compatible binary
layout, whether derived from ATL classes or otherwise.
I would like to use COM classes from managed code because it is more
easier to create UI using WindowsForms than using MFC.
Again, use COM interop for that. It goes both ways. ATL won't help you
at all.
Yes but like VB6 it can only use standard OLE types in interfaces.
I don't believe so. There are attributes to describe any marshallable
type, not just automation-compatible. You may want to ask in
microsoft.public.dotnet.framework.interop.
The only way to consume non standard interfaces is to use #import.
#import only supports automation-compatible interfaces - the same kind
that VB6 also supports. Note that #import takes a type library. Custom
non-automation interfaces are not usually described in the type library.
In fact, many IDL features simply cannot be represented, and are lost,
in the TLB.
And I want to get the simplicity of UI design and the power of
working with COM by using C++/CLI and ATL.
Well, you answered your own question in your original post, haven't you?
You should be able to build a mixed assembly - part managed, part
native.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925