![]() So why not leverage Windows Messaging? After all this is the mechanism unmanaged applications use exactly for this purpose. ![]() However for same-box communications it doesn’t need to be that complex. NET Remoting, it has a lot more functionality than my own implementation and of course is not limited to communication on a single box. The other issue is the lack of helpful error reporting when things go wrong, invariably with permissions.ĭon’t get me wrong, I’m not opposed to. NET Remoting? Well personally in the past I’ve found this extremely tedious to set-up and configure. The library does not implement cross-domain communication across a network, for which case. For example where a task-tray application might want to communicate with (or monitor) a separate desktop application. ![]() The library is intended to send messages between multiple applications in a same-box scenario. NET Remoting would have been impractical (if not impossible), and actually solved more problems than I could have imagined due to its simplicity. It proved to be extremely useful in a number of scenarios where. The XDMessaging library is based on some code developed to aid rapid development for a recent Vista project which required a lot of cross AppDomain communication in a locked-down environment. NET by leveraging Windows native messaging. This article demonstrates a quick and easy-to-use implementation for cross AppDomain communication in.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |