Search: none
Add a search phrase to search resource page titles and descriptions. Different keywords are ANDed with tags.
 

MSDN Archive

Target and filter your gallery search using the following dynamic dialogues.
1-2 of 2Resources < Previous 1 Next >
Resource Page Name and Description Current Release
Makes use of the Nito.Async library to demostrate client and server TCP/IP sockets capable of sending and receiving objects as well as detecting dropped connections.
Makes use of the Nito.Async library to demostrate client and server TCP/IP sockets capable of sending and receiving objects as well as detecting dropped connections.
Popular tags: asynchronous, keepalive, network, packet, Socket, TCP/IP
Downloads: 0 | Started: Jan 23 2009  | Contributors: 1
Re-Building Network Utilities This is a simple network utility that will look for devices on the network. It’s a re-build and re-design of this Coding4Fun article http://blogs.msdn.com/coding4fun/...
Re-Building Network Utilities This is a simple network utility that will look for devices on the network. It’s a re-build and re-design of this Coding4Fun article http://blogs.msdn.com/coding4fun/archive/2006/10/31/914076.aspx. I examined the approach described in this article; however, I couldn’t quite follow the choices made by the author. I implemented the tool using a ThreadPool and provided an interface that offers both my implementation ‘Scan (Thread Pool)’ and the previous implementation ‘Scan (Threads)’. The project explores the System.Net.NetworkInformation namespace, the ListView Control, generics for the callbacks, System.Threading.ThreadPool, and finally form resizing all using Visual Studio 2008 Express Edition. System.Net.NetworkInformation The core functionality of this utility is to ping network addresses to determine what devices might be alive on the network. This becomes almost a trivial task using System.Net.NetworkInformation.Ping. This class sends an ICMP echo request to a specified address. One interesting thing I discovered using the PingReply Class (System.Net.NetworkInformation.PingReply) in the steps above, is that the PingReply.Address will be set to the address of the reply sender. For example, if you send a ping to 123.456.789.000 and that address corresponds to 60.50.40.30, PingReply.Address will be set to 60.50.40.30. In this implementation, I chose not to disclose those translations to the user interface although it might be valuable to add an additional column to show that information to the user. To hide this result, I added IPAddress to the class NetScanCompletedEventArgs.
Popular tags: .NET, ping, network, ListView, C#
Downloads: 0 | Started: Jun 16 2009  | Contributors: 1
NetworkUtilities
Jun 16 2009
Updating...
Page view tracker