M
Mike Fechner
Guest
Hi Nick, I doubt that the OpenClient runtime can be used for your purposes. What you need is an inter process communication solution. In the .NET world, using MS-MQ can be an option. But you’d have to setup that up on every PC. Or you look into establishing this based on something like the .NET bindings for ZeroMQ (0MQ). All you need to deploy in that case is a set of .dll files and ZeroMQ works as a brokerless message queue. Within the same PC that is very easy. When implementing this, you will just have to ensure that you don’t violate the single threaded nature of the AVM. Some of the ZeroMQ .NET bindings word asynchronously and you’d have to build a wrapper around that which synchronizes the events into the WinForms UI thread. Mike Von: NickChild [mailto:bounce-NickChild@community.progress.com] Gesendet: Donnerstag, 7. Mai 2015 09:15 An: PUG-Forum@community.progress.com Betreff: RE: [Progress User Groups - Forum] Openedge from DotNet RE: Openedge from DotNet Reply by NickChild Hi Thanks yes. We already heavily use net in our application and have a rich gui interface using Dev Express controls embedded in progress containers. However what I was specifically asking was...How can I communicate from outside of our application? So for example I write an add-in in Outlook and want to have a button that connects the Progress client and then launches a window. We did this in VB and I was looking for best practice or ideas on how to acheive this using C# or is there any other progress tool available. I was wondering if the Progress.ol4glt.dll could be used to connect to a client rather than an appserver, or is there something similar I could use. nick Stop receiving emails on this subject. Flag this post as spam/abuse.
Continue reading...
Continue reading...