D
David
Hi everyone,
I have a ActiveX EXE component written in VB6. This ActiveX EXE exposes
various public methods that can be called by several other independent
Windows EXE applications (also written in VB6).
I would like to port the ActiveX EXE component it to dotNet. What type of
project that I should port it to? A Windows Service or what? Please suggest.
The thing is that I will not be porting the existing Windows EXE
applications to dotNet yet. So if I port the VB6 ActiveX EXE to a Windows
Service (or anything that is appropriate) will VB6 applications still be
able to communicate with the new dotNet Windows Service (just like they
could with ActiveX EXE)?
Thanks,
David
I have a ActiveX EXE component written in VB6. This ActiveX EXE exposes
various public methods that can be called by several other independent
Windows EXE applications (also written in VB6).
I would like to port the ActiveX EXE component it to dotNet. What type of
project that I should port it to? A Windows Service or what? Please suggest.
The thing is that I will not be porting the existing Windows EXE
applications to dotNet yet. So if I port the VB6 ActiveX EXE to a Windows
Service (or anything that is appropriate) will VB6 applications still be
able to communicate with the new dotNet Windows Service (just like they
could with ActiveX EXE)?
Thanks,
David