bs"d
Hi,

I am working on integrating the "MS Agent" technology into a program.  MS Agent can be accessed through ActiveX or COM protocols.  The "demos" that I have tried use the Visual C++ IDDE to automatically build MFC wrapper classes for the ActiveX interface.  Is there someway to do this with Symantec C++ or Digital Mars?  I tried copying the files created from the MSVC++ build into the Symantec C++ project -- however, when I tried compiling the program I encountered numerous compile errors -- the COM support libraries from SymC++ had slightly different variable declarations than those declared in the MSVC++ produced MFC ActiveX wrapper classes, causing the build to fail.

How do I include an ActiveX project into the Symantec C++ MFC?

Thank you much for your help.

                              Yochanan Spielberg

There was a way to do that kind of stuff in the Symantec^H^H^H^H^H^H^H^HDigitalmars IDDE, however, with all the new development in the COM area I am not so sure if it still works. What I usually do is Just use VC-- to create the type library and stuff like that and create a parallel project in DM IDDE which includes the same files.

Currently I am using the Win32 include directory of M$ Visual Studio.net. I have a patched version of IMPLIB that creates the .lib files from system DLL's. by parsing the header files and calculating the proper @n suffix for the functions.

You actually can create an ActiveX project in DM IDDE with MFC. I think you have to turn on OLE and OCX in Project Settings -> Target.

HTH

Jan



Yochanan Spielberg wrote:

> bs"d
> Hi,
>
> I am working on integrating the "MS Agent" technology into a program.  MS Agent can be accessed through ActiveX or COM protocols.  The "demos" that I have tried use the Visual C++ IDDE to automatically build MFC wrapper classes for the ActiveX interface.  Is there someway to do this with Symantec C++ or Digital Mars?  I tried copying the files created from the MSVC++ build into the Symantec C++ project -- however, when I tried compiling the program I encountered numerous compile errors -- the COM support libraries from SymC++ had slightly different variable declarations than those declared in the MSVC++ produced MFC ActiveX wrapper classes, causing the build to fail.
>
> How do I include an ActiveX project into the Symantec C++ MFC?
>
> Thank you much for your help.
>
>                               Yochanan Spielberg

Hi Jan,

Is the DM IDDE an improvement over the Symantec IDDE?  If so, I may purchase Walter's CD.  I would like to access the new MFC libraries if they are available.

> Currently I am using the Win32 include directory of M$ Visual Studio.net.
I
> have a patched version of IMPLIB that creates the .lib files from system
DLL's.
> by parsing the header files and calculating the proper @n suffix for the functions.

Can you give some more details on this?  Where can I find the patched IMPLIB and documentation?

> You actually can create an ActiveX project in DM IDDE with MFC. I think
you
> have to turn on OLE and OCX in Project Settings -> Target.
>

Thanks.  I will try it.  (Are there sample programs that illustrate these
features?)


               Yochanan


"Jan Knepper" <jan@smartsoft.cc> wrote in message news:3D6DB95C.D0C4BC8D@smartsoft.cc...
> There was a way to do that kind of stuff in the
> Digitalmars IDDE, however, with all the new development
> in the COM area I am not so sure if it still works. What I usually do is
Just
> use VC-- to create the type library and stuff like that and create a
parallel
> project in DM IDDE which includes the same files.
>
> Currently I am using the Win32 include directory of M$ Visual Studio.net.
I
> have a patched version of IMPLIB that creates the .lib files from system
DLL's.
> by parsing the header files and calculating the proper @n suffix for the functions.
>
> You actually can create an ActiveX project in DM IDDE with MFC. I think
you
> have to turn on OLE and OCX in Project Settings -> Target.
>
> HTH
>
> Jan
>
>
>
> Yochanan Spielberg wrote:
>
> > bs"d
> > Hi,
> >
> > I am working on integrating the "MS Agent" technology into a program.
MS
> > Agent can be accessed through ActiveX or COM protocols.  The "demos"
that I
> > have tried use the Visual C++ IDDE to automatically build MFC wrapper classes for the ActiveX interface.  Is there someway to do this with Symantec C++ or Digital Mars?  I tried copying the files created from
the
> > MSVC++ build into the Symantec C++ project -- however, when I tried compiling the program I encountered numerous compile errors -- the COM support libraries from SymC++ had slightly different variable
declarations
> > than those declared in the MSVC++ produced MFC ActiveX wrapper classes, causing the build to fail.
> >
> > How do I include an ActiveX project into the Symantec C++ MFC?
> >
> > Thank you much for your help.
> >
> >                               Yochanan Spielberg
>

Yochanan Spielberg wrote:

> Is the DM IDDE an improvement over the Symantec IDDE?  If so, I may purchase Walter's CD.  I would like to access the new MFC libraries if they are available.

A little I would guess. I have not been able to rebuild the IDDE to executable that do not crash. There is still being worked on it. However, I would concur that some of the patches that have been made actually do improve the IDDE as it is on the CD.

> > Currently I am using the Win32 include directory of M$ Visual Studio.net.
> I
> > have a patched version of IMPLIB that creates the .lib files from system
> DLL's.
> > by parsing the header files and calculating the proper @n suffix for the functions.
> Can you give some more details on this?  Where can I find the patched IMPLIB and documentation?

I will have to email it to you. I do not think it is available through FTP yet.

> > You actually can create an ActiveX project in DM IDDE with MFC. I think
> you
> > have to turn on OLE and OCX in Project Settings -> Target.
> >
> Thanks.  I will try it.  (Are there sample programs that illustrate these
> features?)

There are some examples in samples/mfc32/ole.
As you might know OLE was basically renamed to ActiveX.

Jan