Can this be done ?
-
First of all, I am new to C# and .NET programming, however initial impression is very favourable, despite my brain complaining that it is already full up. Anyway, I am trying to get a client system running a web browser, to exchange text with an application, running on a remote server. I have looked at .NET Remoting and it looks like overkill for what I want to do :omg: So does the panel think the following will work ? Client - Web browser running the DHTML Webservice Behaviour Server - C# WebService talking to - C# Windows Forms Application Seems a simple solution to me :~ however I can't work out the best way to get a C# WebService to talk to a C# application. Appreciation for any help given will be shown with virtual beers (I am sure someone around here uses a beer icon, but I can't see it in the list of smilies) Cheers Steve
-
First of all, I am new to C# and .NET programming, however initial impression is very favourable, despite my brain complaining that it is already full up. Anyway, I am trying to get a client system running a web browser, to exchange text with an application, running on a remote server. I have looked at .NET Remoting and it looks like overkill for what I want to do :omg: So does the panel think the following will work ? Client - Web browser running the DHTML Webservice Behaviour Server - C# WebService talking to - C# Windows Forms Application Seems a simple solution to me :~ however I can't work out the best way to get a C# WebService to talk to a C# application. Appreciation for any help given will be shown with virtual beers (I am sure someone around here uses a beer icon, but I can't see it in the list of smilies) Cheers Steve
For your WebService to talk to your C# application you would again need something like .NET remoting, which brings you back to the first scenario anyways. You are crossing app domains, so communication has to be dealt with anyways. My suggestion would be use .NET remoting. It's really not an overkill at all. The server (which would be you C# application) simply needs add a couple of lines of code. And your client app can add a couple of lines of code and voila!!! You're done!!! The good thing here is that with .NET remoting you have all the flexibilty you want and it's very extensible. You can communicate TCP/IP or Http (through IIS or not) etc... If you need some samples respond back. Steve
-
For your WebService to talk to your C# application you would again need something like .NET remoting, which brings you back to the first scenario anyways. You are crossing app domains, so communication has to be dealt with anyways. My suggestion would be use .NET remoting. It's really not an overkill at all. The server (which would be you C# application) simply needs add a couple of lines of code. And your client app can add a couple of lines of code and voila!!! You're done!!! The good thing here is that with .NET remoting you have all the flexibilty you want and it's very extensible. You can communicate TCP/IP or Http (through IIS or not) etc... If you need some samples respond back. Steve
Many thanks for that, if remoting only needs a few lines of code, then as you say it is not overkill ! I guess the answer then is to connect from the Webservice to the App via TCP/IP. If you have any samples of 'simple' remoting on the same system then that would be great. Cheers Steve M
-
Many thanks for that, if remoting only needs a few lines of code, then as you say it is not overkill ! I guess the answer then is to connect from the Webservice to the App via TCP/IP. If you have any samples of 'simple' remoting on the same system then that would be great. Cheers Steve M
This example exists within the examples of on your computer. \Samples\Technologies\Remoting\Basic\RemotingHello Take 15-30 minutes to look at it. It's worth it.
-
This example exists within the examples of on your computer. \Samples\Technologies\Remoting\Basic\RemotingHello Take 15-30 minutes to look at it. It's worth it.
Hmmm... Took a little while to make the stuff work. My system has 2 network connections. One for the cable set top box for broadband and one for my local network. Add in ZoneAlarm as the firewall and mix until thoroughly confused. IIS on this machine is bound to the local network, BUT it is not resolved to LOCALHOST (i may need to switch network connections over). So I had to edit the .config files to use the actual IP address. The web client implementation wants me to log in as I am not authorized to view the page even though IIS is configured for anonymous acess and so refuses my administrator password :confused::mad: However, running the service using DirectHost service works when using the consoleclient. I have loads of questions but I will carry on playing for while... Cheers Steve