Question

Using AppDomain or possibly Process isolation in a .NET application, I don't necessarily want to give the isolated environment the permissions necessary to create or even open MSMQ MessageQueues. I also don't want to use the isolation channel to have to pass messages back and forth from the privileged host just to enact this as I believe performance would take a big hit.

Is there a way to create/open the MessageQueue in the host and then pass the open handle to the Isolation environment for use (without remoting)?

Was it helpful?

Solution

As you want the other process not to certain privileged operations on MessageQueue I would suggest to abstract it completely rather than passing the handle to the other process as that be a leaky abstraction. Performance wont be a concern if you design proper interface between the 2 process to communicate with each other.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top