Well, in case that 2 processes are involved, the easy approach I described is not applicable indeed. Nevertheless there are more flexible ways to have different processes talk to each other than old-school Windows messages. One technique are so-called named pipes:
Fortunately, they became pretty handy with .NET 3.5:
Anyway, if your application works like it should, leave the implementation as it is. I'd just recommend having a look at named pipes forfuture uses.
Cheers,
Hans
P.S.: As long as no inconsistencies or exceptions occur, thread unsafe GUI updates are no issue. But when they come, you'll know whatto look for! 😉
Well, in case that 2 processes are involved, the easy approach I described is not applicable indeed. Nevertheless there are more flexible ways to have different processes talk to each other than old-school Windows messages. One simple technique are so-called named pipes:
http://msdn.microsoft.com/en-us/library/aa365590(VS.85).aspx
Fortunately, they became pretty handy with .NET 3.5:
http://www.switchonthecode.com/tutorials/dotnet-35-adds-named-pipes-support
A different, much more powerful (and elaborate) way to transfer data between loosely coupled components is MSMQ:
http://msdn.microsoft.com/en-us/library/ms711472(VS.85).aspx
MSMQ is something that really rocks, I absolutely love it and I could cry about the fact that it's so little known.
Anyway, if your application works like it should, leave the implementation as it is. I'd just recommend having a look at named pipes and the like for future uses.
Cheers,
Hans
P.S.: As long as no inconsistencies or exceptions occur, thread unsafe GUI updates are no issue. But when they come, you'll know what to look for! 😉
