StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2106127
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-01-21T00:34:55.340
FavoriteCount
0
LastActivityDate
2010-07-13T17:42:31.513
LastEditDate
2010-07-13T17:42:31.513
LastEditorUserId
0
OwnerUserId
0
ParentId
2105728
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
user220583
text
Body
Ah I love threading. It makes programs so much more interesting... So as I started off learning about how to make responsive applications I came across the function: Application.DoEvents() <a href="http://msdn.microsoft.com/en-us/library/system.windows.forms.application.doevents.aspx" rel="nofollow noreferrer">(http://msdn.microsoft.com/en-us/library/system.windows.forms.application.doevents.aspx)</a> What this does is causes your form to process some of the window events it's receiving. I think that your code could change to include a call after each ping request... i.e. within the on click event handler <pre><code>count = 0; for (int j = 1; j < 255; j++) for (int i = 1; i < 255; i++) { Ping ping = new Ping(); PingReply pingreply = ping.Send(IPAddress.Parse(locip[0] + "." + locip[1] + "." + j + "." + i)); if (pingreply.Status == IPStatus.Success) { status = "o"; repAddress = pingreply.Address.ToString(); ; repRoundtrip = pingreply.RoundtripTime.ToString(); repTTL = pingreply.Options.Ttl.ToString(); repBuffer = pingreply.Buffer.Length.ToString(); string[] lineBuffer = { status, repAddress, repRoundtrip, repTTL, repBuffer }; ipList.Rows.Add(lineBuffer); count += 1; progressBar.Value += 1; } Application.DoEvents(); //but not too often. } </code></pre> Now this was back in the pre dot net days and it's survived till now however, it's not something that you should take lightly. If you click another button on the form it will start off another thread that will attempt to execute and if you're not careful cause thread exceptions on your form. Some developers will tell you don't use this but since your starting off I'd say give it a shot :) I might not use this method depending on the application. Instead what I would do it actually do is to create several processing "trains"; one for each cpu core that the system had. I'd add the ips to be scanned to a queue object and then I would start up 2 to 4 instances of threads (<a href="http://msdn.microsoft.com/en-us/library/system.threading.thread.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/system.threading.thread.aspx</a>) each of which taking an item off the queue in turn, process the information (i.e. do the ping logic) and put the result on another queue; and output queue. Every time a train would finish an item for work it would raise an event at the other end of which there would be a handler in the form. Using the Invoke to make thread safe calls (<a href="http://msdn.microsoft.com/en-us/library/ms171728.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/ms171728.aspx</a>) on my form I would update the UI's information accordingly. Threading is fun dude :) over time you can find that you can use MSMQ to make a system that uses the multicores of other computers to do jobs such as image processing (or something with pa....... ;)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POThreading issues using Ping to map active IPs - C#
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. This table or related slice is empty.
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.