Re: WinForm App to Telnet Application

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: William Stacey [MVP] (staceywREMOVE_at_mvps.org)
Date: 06/03/04 

Date: Thu, 3 Jun 2004 15:49:27 -0400

Please expand a little if possible. What are you doing? The windows app
can be hosted in a telnet session? 

-- 
William Stacey, MVP
"scorpion53061" <admin@nospampleasekjmsolutions.com> wrote in message
news:uoITzVZSEHA.504@TK2MSFTNGP11.phx.gbl...
> This is what I do for a living. I make windows applications that
> interact with telnet connections.
>
> I could help you. Please email me off list. Remove "nospamplease" from
> my email address.
>
> "William Stacey [MVP]" <staceywREMOVE@mvps.org> wrote in message
> news:etieS1QSEHA.3944@tk2msftngp13.phx.gbl:
> > I don't see how a product would even begin to convert a WinForm to a
> > console
> > based app.  How would you handle buttons, list boxes, etc, etc.  I would
> > right a good api in the app that exposes its functionality (kinda like
> > wmi
> > the app.)  Then you can export those apis via Remoting or locally to
> > your
> > telnet server.  If you want a Dos Edit kind of console gui, then your
> > talking more then Telnet.  If your talking just console stuff like enum
> > this, show that, etc.  Then you can create a console front end to each
> > program which can talk to the "server" side remotely using sockets or
> > Remoting.  User could telnet into server and start the console program
> > in
> > interactive or cmdline mode without needing special telnet server -
> > could
> > just use standard server.  Making console version of each program is
> > probably best bet and can be leveraged across Remoting, console clients,
> > hosting app as service, etc.  If this is primary for client, I would
> > recommend all new programs are written as "headless" services and they
> > write
> > gui clients and console clients to interact with services.
> >
>
Quantcast