Winforms and .Net Remoting

[Bill Gower]

I have a client that has users all over the midwest and wants to have them
be able to access the company database on a server in Chicago. Right now
they are using terminal server to have users connect to the server and then
start up my app and when done they log off. This is not the ideal way to do
it and it gets expensive with all the licenses needed. I really don't want
to do an ASP.net app. I really would like to create a Winforms app that
will run on the clients machine and still be able to access the server
database through a VPN. Is this possible with .Net remoting?

Bill

 

[Mr. Arnold]

I have a client that has users all over the midwest and wants to have them
be able to access the company database on a server in Chicago. Right now
they are using terminal server to have users connect to the server and then
start up my app and when done they log off. This is not the ideal way to
do it and it gets expensive with all the licenses needed. I really don't
want to do an ASP.net app. I really would like to create a Winforms app
that will run on the clients machine and still be able to access the server
database through a VPN. Is this possible with .Net remoting?

Yeah it's possible. .Net Remoting will allow you to choose the TCP port to
be used, which should be one of the high ports above 1024 that's not being
used by another application. Your Windows desktop client program will be
making contact with a server program that's sitting there listening.

Or you can use a Windows desktop Web solution with .Net Remoting using
Binary over HTTP port 80 with the Web server acting as a application portal,
sending unanchored serialized binary objects to/from the client and server
programs, which was my first .Net solution I put into production.