Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 353413
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 12, 20262026-05-12T11:49:40+00:00 2026-05-12T11:49:40+00:00

I currently use a System.IO.FileSystemWatcher as part of a roll your own message queue

  • 0

I currently use a System.IO.FileSystemWatcher as part of a “roll your own” message queue system (passing XML “messages” between servers using SOAP web services, writing the “messages” to a specific folder on disk where a Windows Service running a FileSystemWatcher pounces on the new “messages” as they arrive and do something productive with them). I wrote this back in the days of .NET 1.0 or 1.1 (I forget which) as an alternative to using COM-interop to whatever the MSMQ SDK was back then. With all of that as background, I’m considering replacing this ad hoc message queuing scheme with a “true” message queuing implementation. Problem is, there doesn’t seem to be an MSMQ equivalent to the FileSystemWatcher to automatically pick new messages off of the queue as they arrive. Is it buried somewhere in the .NET framework or am I going to have to either use polling or leave things they way they are for now?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-12T11:49:40+00:00Added an answer on May 12, 2026 at 11:49 am

    By calling .Receive in an endless thread, it will block until messages arrived, and return when it gets a message. This is the correct way to do it.

    There are also MSMQ Triggers, but you just need the simple .Receive behaviour, AFAICT.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

No related questions found

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.