16,015,166 members
Sign in
Sign in
Email
Password
Forgot your password?
Sign in with
home
articles
Browse Topics
>
Latest Articles
Top Articles
Posting/Update Guidelines
Article Help Forum
Submit an article or tip
Import GitHub Project
Import your Blog
quick answers
Q&A
Ask a Question
View Unanswered Questions
View All Questions
View C# questions
View C++ questions
View Javascript questions
View Visual Basic questions
View .NET questions
discussions
forums
CodeProject.AI Server
All Message Boards...
Application Lifecycle
>
Running a Business
Sales / Marketing
Collaboration / Beta Testing
Work Issues
Design and Architecture
Artificial Intelligence
ASP.NET
JavaScript
Internet of Things
C / C++ / MFC
>
ATL / WTL / STL
Managed C++/CLI
C#
Free Tools
Objective-C and Swift
Database
Hardware & Devices
>
System Admin
Hosting and Servers
Java
Linux Programming
Python
.NET (Core and Framework)
Android
iOS
Mobile
WPF
Visual Basic
Web Development
Site Bugs / Suggestions
Spam and Abuse Watch
features
features
Competitions
News
The Insider Newsletter
The Daily Build Newsletter
Newsletter archive
Surveys
CodeProject Stuff
community
lounge
Who's Who
Most Valuable Professionals
The Lounge
The CodeProject Blog
Where I Am: Member Photos
The Insider News
The Weird & The Wonderful
help
?
What is 'CodeProject'?
General FAQ
Ask a Question
Bugs and Suggestions
Article Help Forum
About Us
Search within:
Articles
Quick Answers
Messages
Comments by mitchmcc (Top 4 by date)
mitchmcc
5-Aug-11 19:59pm
View
This code is very basic. There is no listener. Once you create the UDPClient, you have to pass the IPEndPoint to the receive method so it can tell the app where the datagram came from. There are many examples of C# UDP Clients that show this technique.
mitchmcc
4-Aug-11 14:19pm
View
Michael, thanks for your help. It did help me figure out the problem. Believe it or not, it appeared that there was some type of invalid character in my .config file, and this was (I believe) causing the service to essentially crash before it really even got started. This meshes with what I saw!
Thanks again, and my advice to everyone is to check your .config file!
mitchmcc
26-Jul-11 11:08am
View
I know I can put in a breakpoint and get it to stop somewhere useful, but in this instance, I knew (or at least suspected) that it was blocked inside a MessageQueue.Receive() call, but the "break all" does NOT show this in the call stack trace, as I would have expected.
mitchmcc
26-Jul-11 11:06am
View
When I "break all", the call stack shows the same place I mentioned in my original post, which is not really where the program is running (I know it is always busy, and expect to see where in the main program logic it is).