Both unmanged and managed TCP/IP Support

[Greg Roberts]

Hi

I was wondering if there are some issues with socket support in this
situation :

- Main program is unmanaged C/C++ which is using windows sockets for its
coms to other unmanaged programs
- The program includes some new C# managed components (via unmaged to
managed interfaces) which
internally are using .NET framework sockets for its coms (to another server
component also in .NET)

I am hoping the unmanaged / managed situation is just the same as an
unmanaged program with multiple thread listening
and using sockets ?

Thanks in advance

[Nicholas Paldino [.NET/C# MVP]]

Greg,

There shouldn't be any problem. A socket is a socket. In this
situation, it's about the protocol (which is up to you to design), and
adhering to it on both sides.

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Greg Roberts" <gr*********@NOSPAMLOWLIFEcitect.com> wrote in message
news:ut*************@TK2MSFTNGP14.phx.gbl...

Hi

I was wondering if there are some issues with socket support in this
situation :

- Main program is unmanaged C/C++ which is using windows sockets for its
coms to other unmanaged programs
- The program includes some new C# managed components (via unmaged to
managed interfaces) which
internally are using .NET framework sockets for its coms (to another
server component also in .NET)

I am hoping the unmanaged / managed situation is just the same as an
unmanaged program with multiple thread listening
and using sockets ?

Thanks in advance