Hi,

looking at your description i see a few options, but i don't know all
the requirements so feel free to ignore any one of those if it doesn't
fit with your timeline, project or thoughts!

Option 1:
- Take the VC++/MFC and move it to C++-CLI/WinForms.
 Requires a reimplementation of the VC++/MFC part for upgrading to
the new CLR C++ standards. WS support is now default available.

Option 2:
- Write a entrypoint DLL in C++/CLI and link with your existing
VC++/MFC program.
 Requires extensive knowlege about "calling conventions" and
"CLR/Native Win32 boundary crossing". WS support is availble in the
.Net DLL (1 abstraction layer)

Option 3:
- Write a COM (interop) exposed .Net type in the .Net language of
choice which exposes the WS functionality through a COM interface.
WS support is available in the .Net COM exposed object (2 abstraction
layers)

I think;
Option 1 is the cleanest, but most expensive.
Option 2 is the 'most straight forward & performing' version, but
requires expert knowlege.
Option 3 is the 'easiest development'. You can continue using COM
objects (which is probably very familiair to you). The negative side
being the performance (crossing the boundaries).

Hope this helps,

Marvin Smit.