Nice job, kunkel!! 

1. An occasional random crash -- i can provide details if you can't reproduce.That would be wonderful.
2. An error message about not understanding what "DoNothing" action means. Funny how computers have a hard time understanding "do nothing", i've never had a problem understanding that myself -- in fact i'm quite good at it.That would be a slight mistake on my part. I recently changed to enums from Strings, and may have accidentally left a space somewhere.
3. Both 1+2 may have to do with the fact that the "what to do" action should be a "Drop Down List" in windows control parlance, rather than a "Drop Down"; the difference being that the former only allows user to choose among those items listed, where the latter also allows user to type in random text.Agreed. I'll make the adjustment.
Another question is how it decides whether the network is up or not.. With multiple network adapters it would seem like the way to do this is either to let user select the adapters/networks to test for up/down, OR test interenet connectivity in general. Not sure what NetLaunch does..I tests all available interfaces, excluding preset blacklisted adapters (virtual and VPN adapters)
I tests all available interfaces, excluding preset blacklisted adapters (virtual and VPN adapters)
and after testing all, how do you conclude if network is up or not? is it that if ANY adapter is up, the network is considered up?
this would be the main thing that could prevent the program from actually being usable for real world scenarios, since it could be pretty common that some network adapters will show as up when the user considers their network (internet?) down.. maybe the solution is being able to specify what network adapter to test, or whether the test should be done simply by pinging a web page, etc.

All of a sudden it keeps crashing with a system.invalidoperationexception.
It is primarily in 1.0, but I tried 1.0.1 and it is having the same issue.

I can recreate it and get the system dump information if that will help any.
P.S. Man, no matter how much I try to plan how long a screencast takes, it is 2 to 3 times longer to actually accomplish. This is harder than I thought it would be. Good to learn though.

Ack, came back to see if you posted a comment about my issues and I missed it. Found that my post with the full error report never posted!
So anyway, I will post now with my appologies that I didn't verify I posted them sooner.
Everything else was in one of those reports for Microsoft, but I was unable to copy any of them out of the "view report" except by taking a great many screenshots. I believe, though, that they really won't help you anyway. They looked like OS related errors rather than application errors, though they may be related....

Original address: https://www.donationcoder.com/forum/index.php?topic=22996.0