Thanks John,
I'll do some searching (codeproject maybe) to see if I can find some
socket Client/Server code to use.
I did see that Remoting and WCF were options. And so I may do that -
but it looks like MS has made Remoting from ASP.NET into a process
more complicated than necessary and we know sockets just work,
regardless.
DC
On Jan 15, 1:49 am, "John Timney \(MVP\)"
<xyz_j...@timney.eclipse.co.ukwrote:
A simple socket server and listener would likely suffice. You would need to
add the socket server code to your existing myServerApp and addd the client
conenction code to an asp.net page.
Regards
John Timney (MVP)http://www.johntimney.comhttp://www.johntimney.com/blog
"bangeye" <davecl...@gmail.comwrote in message
news:16**********************************@f3g2000h sg.googlegroups.com...
Tribe,
I have need to use ASP.NET to connect to an already running
application (non web) that will be running on the same server as IIS.
Start MyServerApp,
MyServerApp is now running - doing work for me.
ASP.NET page request comes in,
Create on the fly object of some sort that can talk to MyServerApp,
Retrieve status from MyServerApp,
Return status to user in web page.
Any ideas?
I do not want to pass data through semaphores, or use the MSMQ to
shuffle messages.
I figure I'll probably have to use a custom socket connection to
exchange data.
Anybody have a reference to something like this?
Thanks,
Dave Cline
~bangeye~