programming Sending data from one winforms application to another winforms application in different computer

[Shammikit]

i want to have 2 applications in 2 separate computers where one will have a form with couple of text boxes and when user inputs in them and press a button i want to send that user input to the other application in the other computer and store it in 2 variables so i can use them for like storing in databases,etc.. How can i achieve this? Please keep the replies simple as im not super good in programming. Thanks

[trag1c]

Winsock library programming isn't overly complex. I am assuming you're using C# since you stated your using winforms. I don't know the specifics for a C# implementation but there should be some documentation on winsocks online.

[Shammikit]

7 minutes ago, trag1c said:

Winsock library programming isn't overly complex. I am assuming you're using C# since you stated your using winforms. I don't know the specifics for a C# implementation but there should be some documentation on winsocks online.

yes im using C# and thanks, i'll go and see about it 

[_dope_]

I would recommend you WCF. 

Its very simple and made for .net languages.

 

Basic:

https://docs.microsoft.com/en-us/dotnet/framework/wcf/whats-wcf

 

Sample: 

https://www.codeproject.com/Articles/97204/Implementing-a-Basic-Hello-World-WCF-Service

[madknight3]

14 hours ago, trag1c said:

Winsock library programming isn't overly complex. I am assuming you're using C# since you stated your using winforms. I don't know the specifics for a C# implementation but there should be some documentation on winsocks online.

14 hours ago, Shammikit said:

yes im using C# and thanks, i'll go and see about it 

Socket programming in a managed .NET application (like the C# WinForms app being used) is normally done using the System.Net.Sockets namespace, not using WinSock.

 

There is the basic Socket class that you can use that is very flexible.

Quote

The Socket class is not protocol specific and provides an abstraction for network communication. This way you can write code using a single set of semantics (Bind, Connect, Send, Receive, etc) regardless of the network protocols you wish you use. For example, you can write a Sockets-based application that uses IPv4 or IPv6 (and more ) as the network layer.

Source

 

 .NET also provides some protocol specific classes that can help make things easier.

• For TCP sockets you have the TcpClient and TcpListener classes.
• For UDP sockets you have the UdpClient class.

These classes use the Socket class underneath, but do a lot of things for you.